Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

99 participants
7051 discussions

[PATCH v4 0/5] rust / dma_buf: Add abstractions for dma_fence

by Philipp Stanner

Changes since v3: - Add a FIXME for an encountered Rust compiler bug. (Gary) - Add new Rust files also to DRM drivers & common infrastructure MAINTAINERS file. (Danilo) - Reposition ECANCELED error code. (Miguel) - Replace refcounted FenceCtx in DriverFenceData with a reference plus life time. (Boris) - Re-add rcu_barrier() patch, since we now can use it for dropping the fence context. (Danilo) - Add forgotten R-b from Alice, and Acks for MAINTAINERS from Christian and Sumit. Changes since v2: - Don't drop DriverFenceData as a whole, but only the members we really want to drop. Gives more robustness. (Gary). - Break apart large pin_init_from_closure(). (Danilo, Onur) - Remove rcu_barrier() and synchronize_rcu() from FenceCtx::drop(). FenceCtx might drop in atomic context, where you must not perform those operations. With the current way C dma_fence is designed, the driver must wait for a grace period manually until it unloads. - Repair the DriverFenceBorrow implementation, properly injecting a life time into it. (Danilo) - Fix memory layout bug for rcu_head. (Onur) - Drop RCU patches, since this series doesn't need them anymore. Changes since v1: - Remove unnecessary mutable references (Alice) - Split up unsafe comments where possible (Danilo) - Remove PhantomData + implement FenceCtx ops trait (Boris) - Consistently call FenceCtx generic data `T`. FenceDataType is derived from that. (Boris) - Add abstractions for call_rcu() and synchronize_rcu() (Danilo) - Add ECANCELED error code in Rust (Alice) - Remove the rcu_barrier() from FenceCtx::drop() – because we now use call_rcu(), there can be no UAF access to the FenceCtx anymore. In any case, it is illegal to use either call_rcu() or synchronize_rcu() in FenceCtx::drop(), because our new drop_driver_fence_data() can run in atomic context and might put the last fence_ctx reference. So we now only have to guard against module unload, which it seems either the driver or Rust driver-core / module unload infrastructure must solve. - Minor formatting etc. changes - Add C helpers to MAINTAINERS. (Danilo) - Ensure that `Fence::is_signaled()` is fully synchronized, i.e., all callbacks really have run. See [1] and [2]. (Myself, Christian König) Changes since the RFCs: - Include support for ForeignOwnable for ARef, so that a Fence can be stuffed into an XArray et al. (Code by Danilo) - Implement ForeignOwnable (with new borrow type) for DriverFence, so that it can be stuffed into an XArray. - Include the rcu::RcuBox data type to defer dropping data with RCU (Cody by Alice) - Port DmaFence to RcuBox to make UAF bugs through later, new dma_fence callbacks (backend_ops) impossible. - Force users to pass their fence data in an RcuBox (or have it not need drop()) through a Sealed trait. - Document the rules for the user's DriverFence::data's drop implementation very clearly (deadlock danger). - rustfmt, Clippy. - Various style suggestions, safety comments, etc. (Önur) - Add __rust_helper prefix to helper functions. (Önur) Changes in RFC v3: - Omit JobQueue patches for now - Completely redesign the memory layout: Instead of a Fence refcounting a DriverFence, both now live in the same allocation to allow for future support the dma_fence backend_ops callbacks which need to do container_of. (mostly Boris's feedback) - Allow for pre-allocating fences to avoid deadlocks when submitting jobs to a GPU. (Boris) - Simultaneously, allow for pre-preparing fence callback objects, so the driver can allocate them when it sees fit. (code largely stolen and inspired by Daniel). - Signal fences on drop, ensure synchronization. - Force users to set an error code when signalling. - Write more documentation - A ton of minor other changes. [1] https://lore.kernel.org/dri-devel/20260608142436.265820-2-phasta@kernel.org/ [2] https://lore.kernel.org/dri-devel/20260612104251.2264707-2-phasta@kernel.or… Alright, so since the last RFCs did not reveal significant design issues, I decided to transition this series to a v1 and hope that we can get it upstream. This now includes code for more common infrastructure that dma_fence needs, contributed by Danilo and Alice. --- Old cover letter for RFC: So, this is the spiritual successor of the first / second RFC [1]. v2 also contained code for drm::JobQueue, but mostly to show how the fence code would be used. JobQueue is under heavy rework right now, so I don't want to bother your eyes with it. The docstring examples should show how Rust fences are supposed to be used, though. This v3 contains a huge amount of highly valuable feedback from a variety of people, notably Boris, but also from Alice, Gary and Danilo. There are some TODOs open (a better trait for fence backend_ops and RCU support), but my hope is that this effort is now finally approaching its end. I would greatly appreciate feedback and especially more information about what might be missing to make this usable, which is obviously where Daniel's and Boris's feedback will be valuable once more. Please regard this patch just as what it's titled: an RFC, to discuss a bit more and to inform a broader community about what the current state is and where this is heading at. Many regards, Philipp [1] https://lore.kernel.org/rust-for-linux/20260203081403.68733-2-phasta@kernel… Danilo Krummrich (1): rust: types: implement ForeignOwnable for ARef<T> Philipp Stanner (4): rust: error: Add ECANCELED error code rust: sync: Add abstraction for rcu_barrier() rust: Add dma_fence abstractions MAINTAINERS: Add entry for Rust dma-buf MAINTAINERS | 5 + rust/bindings/bindings_helper.h | 1 + rust/helpers/dma_fence.c | 48 ++ rust/helpers/helpers.c | 1 + rust/kernel/dma_buf/dma_fence.rs | 870 +++++++++++++++++++++++++++++++ rust/kernel/dma_buf/mod.rs | 14 + rust/kernel/error.rs | 1 + rust/kernel/lib.rs | 1 + rust/kernel/sync/aref.rs | 39 ++ rust/kernel/sync/rcu.rs | 6 + 10 files changed, 986 insertions(+) create mode 100644 rust/helpers/dma_fence.c create mode 100644 rust/kernel/dma_buf/dma_fence.rs create mode 100644 rust/kernel/dma_buf/mod.rs base-commit: 848bf57e98e1678ce7a49eb4e0bf0502da95dc07 -- 2.54.0

1 hour, 35 minutes

Re: [PATCH] drm/gem: modernize locks to use scoped_guard()

by Thomas Zimmermann

Hi Am 16.06.26 um 20:19 schrieb Biren Pandya: > Several GEM core functions manually managed mutex_lock() and > mutex_unlock() over single scopes or error paths. This adds boilerplate > and carries the risk of lock leaks if error paths are refactored. > > Modernize these locks by deploying the <linux/cleanup.h> scoped_guard() > macro. This ensures that the locks are reliably dropped when the block > exits, cleanly removing goto out_unlock paths and tightening the > lifecycle. > > Signed-off-by: Biren Pandya <birenpandya(a)gmail.com> > > Compiled locally, but requires IGT validation by the DRM CI. > --- > drivers/gpu/drm/drm_gem.c | 66 ++++++++++++++++++--------------------- > 1 file changed, 30 insertions(+), 36 deletions(-) > > diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c > index 891c3bff5ae0..d3a061d42ba7 100644 > --- a/drivers/gpu/drm/drm_gem.c > +++ b/drivers/gpu/drm/drm_gem.c > @@ -346,13 +346,13 @@ void drm_gem_object_handle_put_unlocked(struct drm_gem_object *obj) > * we checked for a name. > */ > > - mutex_lock(&dev->object_name_lock); > - if (--obj->handle_count == 0) { > - drm_gem_object_handle_free(obj); > - drm_gem_object_exported_dma_buf_free(obj); > - final = true; > + scoped_guard(mutex, &dev->object_name_lock) { > + if (--obj->handle_count == 0) { > + drm_gem_object_handle_free(obj); > + drm_gem_object_exported_dma_buf_free(obj); > + final = true; > + } > } > - mutex_unlock(&dev->object_name_lock); > > if (final) > drm_gem_object_put(obj); > @@ -374,11 +374,8 @@ drm_gem_object_release_handle(int id, void *ptr, void *data) > if (obj->funcs->close) > obj->funcs->close(obj, file_priv); > > - mutex_lock(&file_priv->prime.lock); > - > - drm_prime_remove_buf_handle(&file_priv->prime, id); > - > - mutex_unlock(&file_priv->prime.lock); > + scoped_guard(mutex, &file_priv->prime.lock) > + drm_prime_remove_buf_handle(&file_priv->prime, id); > > drm_vma_node_revoke(&obj->vma_node, file_priv); > > @@ -1021,37 +1018,34 @@ int drm_gem_change_handle_ioctl(struct drm_device *dev, void *data, There have been a number of revisions to this function recently and you want to make sure that you have the latest. At least the code in v7.1 looks different from yours. > goto out; > } > > - mutex_lock(&file_priv->prime.lock); > + scoped_guard(mutex, &file_priv->prime.lock) { > + spin_lock(&file_priv->table_lock); Could this spin lock also use a guard? Best regards Thomas > + ret = idr_alloc(&file_priv->object_idr, obj, handle, handle + 1, > + GFP_NOWAIT); > + spin_unlock(&file_priv->table_lock); > > - spin_lock(&file_priv->table_lock); > - ret = idr_alloc(&file_priv->object_idr, obj, handle, handle + 1, > - GFP_NOWAIT); > - spin_unlock(&file_priv->table_lock); > + if (ret < 0) > + break; > > - if (ret < 0) > - goto out_unlock; > + if (obj->dma_buf) { > + ret = drm_prime_add_buf_handle(&file_priv->prime, obj->dma_buf, > + handle); > + if (ret < 0) { > + spin_lock(&file_priv->table_lock); > + idr_remove(&file_priv->object_idr, handle); > + spin_unlock(&file_priv->table_lock); > + break; > + } > > - if (obj->dma_buf) { > - ret = drm_prime_add_buf_handle(&file_priv->prime, obj->dma_buf, > - handle); > - if (ret < 0) { > - spin_lock(&file_priv->table_lock); > - idr_remove(&file_priv->object_idr, handle); > - spin_unlock(&file_priv->table_lock); > - goto out_unlock; > + drm_prime_remove_buf_handle(&file_priv->prime, args->handle); > } > > - drm_prime_remove_buf_handle(&file_priv->prime, args->handle); > - } > - > - ret = 0; > - > - spin_lock(&file_priv->table_lock); > - idr_remove(&file_priv->object_idr, args->handle); > - spin_unlock(&file_priv->table_lock); > + ret = 0; > > -out_unlock: > - mutex_unlock(&file_priv->prime.lock); > + spin_lock(&file_priv->table_lock); > + idr_remove(&file_priv->object_idr, args->handle); > + spin_unlock(&file_priv->table_lock); > + } > out: > drm_gem_object_put(obj); > > > base-commit: 72c25183cac9bc584c9de21797a5883af44bcc7a -- -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)

1 hour, 52 minutes

Re: [PATCH] drm/gem: modernize locks to use scoped_guard()

by Laurent Pinchart

On Mon, Jun 22, 2026 at 06:22:27PM +0530, biren pandya wrote: > On Mon, Jun 22, 2026 at 5:25 PM Laurent Pinchart wrote: > > On Tue, Jun 16, 2026 at 11:49:57PM +0530, Biren Pandya wrote: > > > Several GEM core functions manually managed mutex_lock() and > > > mutex_unlock() over single scopes or error paths. This adds boilerplate > > > and carries the risk of lock leaks if error paths are refactored. > > > > > > Modernize these locks by deploying the <linux/cleanup.h> scoped_guard() > > > macro. This ensures that the locks are reliably dropped when the block > > > exits, cleanly removing goto out_unlock paths and tightening the > > > lifecycle. > > > > What's the reason for doing so in in drm_gem and not other areas in DRM > > ? > > Hi Laurent, > > Thanks for taking a look. > No deeper reason than it being where I happened to start — I didn't > mean to single it out, and I'd rather the treatment be consistent than > piecemeal. > > > > @@ -1021,37 +1018,34 @@ int drm_gem_change_handle_ioctl(struct drm_device *dev, void *data, > > > goto out; > > > } > > > > > > - mutex_lock(&file_priv->prime.lock); > > > + scoped_guard(mutex, &file_priv->prime.lock) { > > > + spin_lock(&file_priv->table_lock); > > > + ret = idr_alloc(&file_priv->object_idr, obj, handle, handle + 1, > > > + GFP_NOWAIT); > > > + spin_unlock(&file_priv->table_lock); > > > > And why don't you use guards for the spinlock as well ? > > Fair point — the spinlocks here are equally good candidates; I only > kept v1 to mutexes to keep it small. > > That said, this is a pure cleanup with no functional change, so it's > entirely your call whether it's worth carrying. > If you'd like it, I'll send a v2 that converts both the mutexes and > the spinlocks in drm_gem.c consistently. If you'd prefer not to take > cleanup-only churn, I'm happy to drop it — no problem either way. I'll let the maintainers of that code decide (I'm not one of them). -- Regards, Laurent Pinchart

2 hours, 30 minutes

Re: [PATCH] drm/gem: modernize locks to use scoped_guard()

by Laurent Pinchart

On Tue, Jun 16, 2026 at 11:49:57PM +0530, Biren Pandya wrote: > Several GEM core functions manually managed mutex_lock() and > mutex_unlock() over single scopes or error paths. This adds boilerplate > and carries the risk of lock leaks if error paths are refactored. > > Modernize these locks by deploying the <linux/cleanup.h> scoped_guard() > macro. This ensures that the locks are reliably dropped when the block > exits, cleanly removing goto out_unlock paths and tightening the > lifecycle. What's the reason for doing so in in drm_gem and not other areas in DRM ? > Signed-off-by: Biren Pandya <birenpandya(a)gmail.com> > > Compiled locally, but requires IGT validation by the DRM CI. > --- > drivers/gpu/drm/drm_gem.c | 66 ++++++++++++++++++--------------------- > 1 file changed, 30 insertions(+), 36 deletions(-) > > diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c > index 891c3bff5ae0..d3a061d42ba7 100644 > --- a/drivers/gpu/drm/drm_gem.c > +++ b/drivers/gpu/drm/drm_gem.c > @@ -346,13 +346,13 @@ void drm_gem_object_handle_put_unlocked(struct drm_gem_object *obj) > * we checked for a name. > */ > > - mutex_lock(&dev->object_name_lock); > - if (--obj->handle_count == 0) { > - drm_gem_object_handle_free(obj); > - drm_gem_object_exported_dma_buf_free(obj); > - final = true; > + scoped_guard(mutex, &dev->object_name_lock) { > + if (--obj->handle_count == 0) { > + drm_gem_object_handle_free(obj); > + drm_gem_object_exported_dma_buf_free(obj); > + final = true; > + } > } > - mutex_unlock(&dev->object_name_lock); > > if (final) > drm_gem_object_put(obj); > @@ -374,11 +374,8 @@ drm_gem_object_release_handle(int id, void *ptr, void *data) > if (obj->funcs->close) > obj->funcs->close(obj, file_priv); > > - mutex_lock(&file_priv->prime.lock); > - > - drm_prime_remove_buf_handle(&file_priv->prime, id); > - > - mutex_unlock(&file_priv->prime.lock); > + scoped_guard(mutex, &file_priv->prime.lock) > + drm_prime_remove_buf_handle(&file_priv->prime, id); > > drm_vma_node_revoke(&obj->vma_node, file_priv); > > @@ -1021,37 +1018,34 @@ int drm_gem_change_handle_ioctl(struct drm_device *dev, void *data, > goto out; > } > > - mutex_lock(&file_priv->prime.lock); > + scoped_guard(mutex, &file_priv->prime.lock) { > + spin_lock(&file_priv->table_lock); > + ret = idr_alloc(&file_priv->object_idr, obj, handle, handle + 1, > + GFP_NOWAIT); > + spin_unlock(&file_priv->table_lock); And why don't you use guards for the spinlock as well ? > > - spin_lock(&file_priv->table_lock); > - ret = idr_alloc(&file_priv->object_idr, obj, handle, handle + 1, > - GFP_NOWAIT); > - spin_unlock(&file_priv->table_lock); > + if (ret < 0) > + break; > > - if (ret < 0) > - goto out_unlock; > + if (obj->dma_buf) { > + ret = drm_prime_add_buf_handle(&file_priv->prime, obj->dma_buf, > + handle); > + if (ret < 0) { > + spin_lock(&file_priv->table_lock); > + idr_remove(&file_priv->object_idr, handle); > + spin_unlock(&file_priv->table_lock); > + break; > + } > > - if (obj->dma_buf) { > - ret = drm_prime_add_buf_handle(&file_priv->prime, obj->dma_buf, > - handle); > - if (ret < 0) { > - spin_lock(&file_priv->table_lock); > - idr_remove(&file_priv->object_idr, handle); > - spin_unlock(&file_priv->table_lock); > - goto out_unlock; > + drm_prime_remove_buf_handle(&file_priv->prime, args->handle); > } > > - drm_prime_remove_buf_handle(&file_priv->prime, args->handle); > - } > - > - ret = 0; > - > - spin_lock(&file_priv->table_lock); > - idr_remove(&file_priv->object_idr, args->handle); > - spin_unlock(&file_priv->table_lock); > + ret = 0; > > -out_unlock: > - mutex_unlock(&file_priv->prime.lock); > + spin_lock(&file_priv->table_lock); > + idr_remove(&file_priv->object_idr, args->handle); > + spin_unlock(&file_priv->table_lock); > + } > out: > drm_gem_object_put(obj); > > > base-commit: 72c25183cac9bc584c9de21797a5883af44bcc7a -- Regards, Laurent Pinchart

3 hours, 36 minutes

BOVET RECITAL 16 Triple Time Zone Tourbillon Watch

by fashionluxurybazaar1004＠gmail.com

BOVET RECITAL 16 Triple Time Zone Tourbillon Watch Classic and traditional, the Bovet Recital collection is stunning, and this latest 16-time-zone triple time zone tourbillon watch is truly exceptional. Belonging to the Dimier series, its distinctive feature is the absence of the "ribbon" crown guard at 12 o'clock. Therefore, despite its complex and intricate design, the crown at 3 o'clock retains a very traditional style. This watch is powered by the "Calibre Rising Star II" mechanical movement, displaying the time in major cities as well as two other cities. The highlight of this timepiece is that it is not merely an elegant timepiece, but a technical masterpiece and exquisite design. Like its watch collection, the brand is unique, producing not only its own movements but also many components such as the case and dial. Due to its superb craftsmanship, other brands seek their assistance. https://www.chrono-wrist.co.uk/ https://www.moon-watch.co.uk/ https://www.perfectwrist.co/ https://www.reviewluxurystore.com/ Bovet does not follow trends, adhering to its own path and setting the highest standards in the field of design. From top to bottom, the brand upholds a passion for creation, a dedication to quality, and an unyielding pursuit of excellence. The Recital 16 Three Time Zone Tourbillon watch is available in two styles: 18K red gold and 18K white gold. The white gold version is adorned with exquisite decorations, such as mother-of-pearl dials for the second and third time zones, and a bezel set with dazzling baguette-cut diamonds. This 46mm watch is not a slim design, but this is precisely what gives it a masculine feel and makes it exceptionally comfortable to wear. A round blue sapphire crystal is set in the crown, reminiscent of a classic Cartier piece. Adjusting the time is a pleasure in itself, and the simultaneous movement of the three dials is a feast for the eyes. The function of adjusting all time zones simultaneously is simple yet sophisticated, and it can even synchronize the minute hand. The Bovet Recital 16 watch strives to combine practicality with exquisite beauty. You might think that having two additional time zone displays is practical enough, but what's even more surprising is that each time zone also features an independent day/night indicator and a reference city indicator, making it a true travel essential. Since the time zones use a 12-hour system, the day/night indicator is equally useful in other aspects. Buttons on the side of the case allow for easy adjustment of the second and third time zone indicators on the dial. This watch features a 7-day power reserve movement and an open design without a traditional dial, offering a wide field of vision. The hands and markers are coated with luminescent material for excellent legibility, complementing the overall style of the watch. This timepiece will undoubtedly be a collector's item, but the brand positions it as a niche timepiece, designed specifically for consumers who aspire to enter the luxury market.

3 hours, 39 minutes

Sprunki Game – A Musical Adventure Where Each Player Can Create Their Own World

by cranephilip92＠gmail.com

Instead of following a linear storyline or mandatory tasks, sprunki game ( https://musicgames.io/sprunki-2 ) allows players to write their own journey through musical arrangements. Each drag-and-drop, each experiment with a new combination, produces unexpected results, keeping the experience fresh. Most appealing is the limitless power of imagination. Players can create cheerful melodies, deeply emotional tunes, or even mysterious sounds never before heard. This absolute freedom is what makes Sprunki one of the most creative and beloved games in the community today. The biggest difference between Sprunki Game and many other music games lies in its approach to users. Instead of requiring players to perform actions according to pre-set rhythms, Sprunki encourages them to actively create music in their own way. Each character in the game is like a living instrument, possessing a distinct sound and personality. When characters are combined, they form a complete composition with a unique and unreplicable sound. Players don't need professional musical knowledge to create interesting works with just a few simple steps. This is why Sprunki is loved by both music enthusiasts and those who simply want a relaxing form of entertainment. The game makes creativity more accessible than ever and allows everyone to experience the joy of creating a product with their own personal touch.

3 hours, 40 minutes

replica Ulysse Nardin Freak X

by fashionluxurybazaar1004＠gmail.com

Ulysse Nardin Introduces the Freak X Second Generation Watch Smaller, but Better. The second-generation Ulysse Nardin (UN) Freak X watch embodies the concept of "small but perfectly formed," featuring a new micro-rotor movement that powers the Freak collection's iconic "flying carousel" caliber. This new movement debuts in a smaller 41mm stainless steel case and comes with a interchangeable strap system. The new Freak X watch boasts many commendable features. It retains UN's signature "flying carousel" tourbillon structure and houses a new micro-rotor movement, upgraded with the brand's exclusive DiamonSil escapement. The new watch is significantly smaller than its predecessor and offers enhanced water resistance thanks to the collection's first screw-down crown. The interchangeable strap system provides a wider range of strap options, including a stainless steel bracelet. Some may lament the downgrade from titanium to steel, but given the smaller case size, this is a relatively minor issue, and a titanium version is almost certain to be released in the future.   <a href="https://www.moon-watch.co.uk/ulysse-nardin-freak-watches-c-101_104.html">replica Ulysse Nardin Freak X</a> <a href="https://www.moon-watch.co.uk">best replica watches</a> <a href="https://www.moon-watch.co.uk/jacob-and-co-c-8.html">jacob and co replica</a> Smaller, But Better 25 years ago, the Freak watch burst onto the scene, stunning the industry with its innovative structure that integrated the entire time train and escapement into a single large minute hand. While the Freak X simplifies the design concept slightly, incorporating the time train into the dial where the hour hand is located, the overall appearance remains largely unchanged. One of the most striking design elements of the original Freak watch was the absence of a crown—the watch was wound via the case back and adjusted via the bezel. The simplified Freak X adopts a more traditional structure and features a standard crown at 3 o'clock, thus downplaying this design element. The new Freak X retains the crown, but now features a screw-down design to achieve 100-meter water resistance. The crown screws down into a stainless steel case, now reduced from 43mm to 41mm, and the lug spacing has also been shortened to a more comfortable 47.3mm. The case thickness is 13.6mm, roughly between the thinnest version of the previous generation and the version with the art dial (13.78mm). The new box-shaped sapphire crystal absorbs some of the thickness, making it appear even slimmer. <a href="https://www.perfectwrist.ru">perfect watches review</a> <a href="https://www.perfectwrist.co/richard-mille-watches-c-24.html">replica Richard Mille watches</a> <a href="https://www.perfectwrist.co/ulysse-nardin-watches-c-103.html">ulysse nardin replica watches</a>   A damn miniature rotor Although the movement model name has changed slightly—the previous automatic movement was named UN-230—the UN-232 is quite different. The most significant change is the adoption of a jewel-bearing miniature rotor, which differs from most other miniature rotor designs in that it has a supporting bridge above it. This design is reminiscent of certain vintage Universal Geneve movements, such as the 12P, and recent automatic movements by designers like Laurent Ferrier and Romain Gauthier. This movement still uses a mainspring barrel, but by Freak standards, the barrel is rather ordinary. This structure is quite different from the flagship Freak, which occupies almost the entire width of the movement to house a large mainspring barrel. In other words, the upgraded Freak X shares more substantial similarities with its "big brother" in some aspects, such as its DiamonSil escapement. The DiamonSil escapement features a diamond-coated silicon escape wheel and integrated escape fork. The DiamonSil coating is a completely new design for the Freak X—previous versions only used uncoated silicon components. This component transfers energy to a silicon balance wheel mounted on the brand's most advanced oval silicon hairspring, which is carefully designed to improve isochronism. <a href="https://www.whereguidewatch.com">fake luxury watches</a> <a href="https://www.whereguidewatch.com">high quality fake watches</a> <a href="https://www.whereguidewatch.com/jacob-co-c-4.html">replica jacob and co Astronomia watches</a> Interestingly, UN claims that each of its movements is assembled from start to finish by a single watchmaker, a stark contrast to the increasingly prevalent assembly line production methods. While assembly line production can increase output and reduce costs, it is difficult to reconcile with the romantic ideals of haute horlogerie. Ulysse Nardin Freak X Models: 2323-500-1A/0A (Grey), 2323-500-3A/7A (Blue), 2323-500-2A/1A (Gold) Diameter: 41 mm; Height: 13.6 mm; Material: Stainless Steel; Crystal: Sapphire Crystal; Water Resistance: 100 meters Movement: UN-232 Functions: Hours, Minutes Winding: Automatic Frequency: 21,600 vibrations per hour (3 Hz) Power Reserve: 72 hours Strap: Leather strap with a folding clasp in the same color as the case, or stainless steel bracelet

3 hours, 40 minutes

by douglasesmith206＠gmail.com

1 day, 3 hours

by douglasesmith206＠gmail.com

在線購買香港身份證和駕駛執照（微信ID：Wesbutman）在線購買中國身份證和駕駛執照. 在線購買韓國身份證和駕駛執照. 線上購買台灣身分證和駕駛執照. 在線購買泰國身份證和駕駛執照. 在線購買日本身份證和駕駛執照. 在線購買美國身份證和駕駛執照. 在線購買波蘭身份證和駕駛執照. 在線購買身份證和駕駛執照. 在線購買英國身份證和駕駛執照. 在線購買加拿大身份證和駕駛執照. 在線購買挪威身份證和駕駛執照. 在線購買馬來西亞身份證和駕駛執照. 在線購買法國身份證和駕駛執照. 在線購買捷克身份證和駕駛執照. 在線購買巴西身份證和駕駛執照. 在線購買愛沙尼亞身份證和駕駛執照. 购买中国驾驶执照: https://buytraveldocsonline.com/购买中国驾驶执照/ 购买中国身份证: https://buytraveldocsonline.com/购买中国身份证/ 購買韓國身分證: https://buytraveldocsonline.com/購買韓國身分證/ 在線購買日本身份證: https://buytraveldocsonline.com/在線購買日本身份證/ 線上購買台灣身分證: https://buytraveldocsonline.com/線上購買台灣身分證/ 購買韓國身分證: https://buytraveldocsonline.com/buy-korean-id-card/ 購買美國駕照: https://buytraveldocsonline.com/buy-u-s-drivers-license-2/ 在線購買真正的台灣駕照: https://buytraveldocsonline.com/在線購買真正的台灣駕照/ 在线购买意大利驾驶执照: https://buytraveldocsonline.com/在线购买意大利驾驶执照/ 在线购买奥地利驾驶执照: https://buytraveldocsonline.com/在线购买奥地利驾驶执照/ 在线购买欧盟驾驶执照: https://buytraveldocsonline.com/在线购买欧盟驾驶执照/ 在线购买德国驾驶执照: https://buytraveldocsonline.com/在线购买德国驾驶执照/ 購買加拿大永久居民卡: https://buytraveldocsonline.com/購買加拿大永久居民卡/ (WhatsApp：+49 1521 5066462) (微信 ID：Wesbutman) (Telegram：wesbutman0) (信箱：wesbutman0(a)gmail.com) https://buytraveldocsonline.com/ 在線購買阿拉巴馬州駕照。在線購買阿拉斯加州駕照。在線購買亞利桑那州駕照。在線購買阿肯色州駕照。在線購買加州駕照。在線購買科羅拉多州駕照。在線購買康涅狄格州駕照。在線購買特拉華州駕照。在線購買佛羅裡達州駕照。在線購買佐治亞州駕照。在線購買夏威夷州駕照。在線購買愛達荷州駕照。在線購買伊利諾伊州駕照。在線購買印第安納州駕照。在線購買愛荷華州駕照。在線購買堪薩斯州駕照。在線購買肯塔基州駕照。在線購買路易斯安那州駕照。在線購買緬因州駕照。在線購買馬裡蘭州駕照。在線購買馬薩諸塞州駕照。在線購買密西根州駕照。在線購買明尼蘇達州駕照。在線購買密西西比州駕照。在線購買密蘇裡州駕照。在線購買蒙大拿州駕照。在線購買內布拉斯加州駕照。在線購買內華達州駕照。在線購買新罕布什爾州駕照。在線購買新澤西州駕照。在線購買新墨西哥州駕照。在線購買紐約州駕照。在線購買北卡羅來納州駕照。在線購買北達科他州駕照。在線購買俄亥俄州駕照。在線購買俄克拉荷馬州駕照。在線購買俄勒岡州駕照。在線購買賓州駕照。在線購買羅德島州駕照。在線購買南卡羅來納州駕照。在線購買南達科他州駕照。在線購買田納西州駕照。在線購買德克薩斯州駕照。在線購買猶他州駕照。在線購買佛蒙特州駕照。在線購買弗吉尼亞州駕照。在線購買華盛頓州駕照。在線購買西維吉尼亞州駕照。在線購買威斯康辛州駕照。在線購買懷俄明州駕照。購買美國駕照: https://buytraveldocsonline.com/buy-u-s-drivers-license-2/ 在线购买波兰驾驶执照: https://buytraveldocsonline.com/在线购买波兰驾驶执照/ 在线购买瑞典驾驶执照: https://buytraveldocsonline.com/在线购买瑞典驾驶执照/ 在线购买瑞士驾驶执照: https://buytraveldocsonline.com/在线购买瑞士驾驶执照/ 在线购买英国驾驶执照: https://buytraveldocsonline.com/在线购买英国驾驶执照/ 在线购买爱尔兰驾驶执照: https://buytraveldocsonline.com/在线购买爱尔兰驾驶执照/ 在線購買波蘭身份證: https://buytraveldocsonline.com/buy-polish-id-card/ 在線購買比利時身份證: https://buytraveldocsonline.com/buy-belgian-id-card/ 在線購買西班牙身份證: https://buytraveldocsonline.com/buy-spanish-id-card/ 在線購買義大利身份證: https://buytraveldocsonline.com/buy-italian-id-card/ 在線購買新加坡身份證: https://buytraveldocsonline.com/buy-singapore-id-card/ 在線購買歐盟居留許可: https://buytraveldocsonline.com/buy-an-eu-residence-permit-online/ (WhatsApp：+49 1521 5066462) (微信 ID：Wesbutman) (Telegram：wesbutman0) (信箱：wesbutman0(a)gmail.com) https://buytraveldocsonline.com/

1 day, 3 hours

by douglasesmith206＠gmail.com

购买香港护照 (微信ID：Wesbutman) 购买中国护照, 購買韓國護照, 購買正品日本護照, 購買正品美國護照, 購買台灣護照, 購買泰國護照, 購買正品波蘭護照, 購買正品澳洲護照, 購買正品英國護照, 購買正品加拿大護照, 購買正品挪威護照, 在線購買真正的馬來西亞護照,購買正品法國護照, 購買正品捷克護照, 購買正品巴西護照, 購買正品愛沙尼亞護照, 購買真假身分證, 購買台灣身分證, 購買台灣駕照, 購買泰國駕駛執照, 購買泰國身分證, 購買真假簽證, 購買假美元, 購買假CYN, 購買假澳幣, 購買真護照或假護照, 購買真假駕照, 購買真假身分證, 购买香港护照: https://buytraveldocsonline.com/购买香港护照/ 购买中国护照: https://buytraveldocsonline.com/购买中国护照/ 購買正品加拿大護照: https://buytraveldocsonline.com/購買正品加拿大護照/ 購買正品挪威護照: https://buytraveldocsonline.com/購買正品挪威護照/ 在線購買真正的馬來西亞護照: https://buytraveldocsonline.com/在線購買真正的馬來西亞護照/ 在線購買真正的泰國護照: https://buytraveldocsonline.com/在線購買真正的泰國護照/ 購買正品法國護照: https://buytraveldocsonline.com/購買正品法國護照/ 在線購買真正的台灣護照: https://buytraveldocsonline.com/在線購買真正的台灣護照/ 在線購買真正的葡萄牙護照: https://buytraveldocsonline.com/在線購買真正的葡萄牙護照/ 購買正品英國護照: https://buytraveldocsonline.com/購買正品英國護照/ 購買正品澳洲護照: https://buytraveldocsonline.com/購買正品澳洲護照/ 購買正品波蘭護照: https://buytraveldocsonline.com/購買正品波蘭護照/ 購買正品美國護照: https://buytraveldocsonline.com/購買正品美國護照/ 購買正品愛沙尼亞護照: https://buytraveldocsonline.com/購買正品愛沙尼亞護照/ 購買正品巴西護照: https://buytraveldocsonline.com/購買正品巴西護照/ 購買正品捷克護照: https://buytraveldocsonline.com/購買正品捷克護照/ 購買正品日本護照: https://buytraveldocsonline.com/購買正品日本護照/ 購買真正的韓國護照: https://buytraveldocsonline.com/buy-real-korean-passport/ (Telegram：wesbutman0) (WhatsApp：+49 1521 5066462) (微信ID：Wesbutman) (信箱：wesbutman0(a)gmail.com) https://buytraveldocsonline.com 在線購買香港簽證（微信ID：Wesbutman），在線購買中國簽證，在線購買韓國簽證，在線購買正品日本簽證，在線購買正品美國簽證，在線購買台灣簽證，在線購買泰國簽證，在線購買正品波蘭簽證，在線購買正品澳洲簽證，線上購買正品英國簽證，線上購買正品加拿大簽證，線上購買正品挪威簽證，線上購買正品馬來西亞簽證，線上購買正品法國簽證，線上購買正品捷克簽證，線上購買正品巴西簽證，線上購買正品愛沙尼亞簽證在線購買真正的美國visa卡: https://buytraveldocsonline.com/在線購買真正的美國visa卡/ 在線購買真正的中國簽證: https://buytraveldocsonline.com/在線購買真正的中國簽證/ 在線購買真正的台灣簽證: https://buytraveldocsonline.com/在線購買真正的台灣簽證/ 在線購買真正的馬來西亞簽證: https://buytraveldocsonline.com/在線購買真正的馬來西亞簽證/ 在線購買真實的英國簽證: https://buytraveldocsonline.com/buy-real-uk-visa/ 線上購買申根簽證: https://buytraveldocsonline.com/buy-schengen-visa-online/ 在線購買真實的美國簽證: https://buytraveldocsonline.com/buy-real-u-s-visas/ 在線購買真實的新加坡簽證: https://buytraveldocsonline.com/buy-real-singapore-visas/ 在線購買真正的加拿大簽證: https://buytraveldocsonline.com/buy-real-canadian-visas/ 在線購買真正的澳洲簽證: https://buytraveldocsonline.com/buy-real-australian-visas/ 購買加拿大永久居民卡: https://buytraveldocsonline.com/購買加拿大永久居民卡/ (Telegram：wesbutman0) (WhatsApp：+49 1521 5066462) (微信ID：Wesbutman) (信箱：wesbutman0(a)gmail.com) https://buytraveldocsonline.com

1 day, 3 hours

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig