qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 06/16] rust: cell: remove support for running doctests with "cargo test --doc"
Date: Tue,  3 Jun 2025 23:45:13 +0200	[thread overview]
Message-ID: <20250603214523.131185-7-pbonzini@redhat.com> (raw)
In-Reply-To: <20250603214523.131185-1-pbonzini@redhat.com>

This is not needed anymore now that tests link with libqemuutil.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
 rust/qemu-api/src/cell.rs | 22 +++++++++-------------
 1 file changed, 9 insertions(+), 13 deletions(-)

diff --git a/rust/qemu-api/src/cell.rs b/rust/qemu-api/src/cell.rs
index 05ce09f6cb6..27063b049d5 100644
--- a/rust/qemu-api/src/cell.rs
+++ b/rust/qemu-api/src/cell.rs
@@ -225,27 +225,23 @@
 
 /// An internal function that is used by doctests.
 pub fn bql_start_test() {
-    if cfg!(MESON) {
-        // SAFETY: integration tests are run with --test-threads=1, while
-        // unit tests and doctests are not multithreaded and do not have
-        // any BQL-protected data.  Just set bql_locked to true.
-        unsafe {
-            bindings::rust_bql_mock_lock();
-        }
+    // SAFETY: integration tests are run with --test-threads=1, while
+    // unit tests and doctests are not multithreaded and do not have
+    // any BQL-protected data.  Just set bql_locked to true.
+    unsafe {
+        bindings::rust_bql_mock_lock();
     }
 }
 
 pub fn bql_locked() -> bool {
     // SAFETY: the function does nothing but return a thread-local bool
-    !cfg!(MESON) || unsafe { bindings::bql_locked() }
+    unsafe { bindings::bql_locked() }
 }
 
 fn bql_block_unlock(increase: bool) {
-    if cfg!(MESON) {
-        // SAFETY: this only adjusts a counter
-        unsafe {
-            bindings::bql_block_unlock(increase);
-        }
+    // SAFETY: this only adjusts a counter
+    unsafe {
+        bindings::bql_block_unlock(increase);
     }
 }
 
-- 
2.49.0



  parent reply	other threads:[~2025-06-03 21:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 21:45 [PULL 00/16] rust, i386 changes for 2025-06-03 Paolo Bonzini
2025-06-03 21:45 ` [PULL 01/16] rust: bindings: allow ptr_offset_with_cast Paolo Bonzini
2025-06-03 21:45 ` [PULL 02/16] meson: update to version 1.8.1 Paolo Bonzini
2025-06-03 21:45 ` [PULL 03/16] rust: use "objects" for Rust executables as well Paolo Bonzini
2025-06-03 21:45 ` [PULL 04/16] build, dockerfiles: add support for detecting rustdoc Paolo Bonzini
2025-06-03 21:45 ` [PULL 05/16] rust: add qemu-api doctests to "meson test" Paolo Bonzini
2025-06-03 21:45 ` Paolo Bonzini [this message]
2025-06-03 21:45 ` [PULL 07/16] rust: use native Meson support for clippy and rustdoc Paolo Bonzini
2025-06-03 21:45 ` [PULL 08/16] target/i386: Remove FRED dependency on WRMSRNS Paolo Bonzini
2025-06-03 21:45 ` [PULL 09/16] target/i386: Add a new CPU feature word for CPUID.7.1.ECX Paolo Bonzini
2025-06-03 21:45 ` [PULL 10/16] target/i386: Add the immediate form MSR access instruction support Paolo Bonzini
2025-06-03 21:45 ` [PULL 11/16] meson: use config_base_arch for target libraries Paolo Bonzini
2025-06-03 21:45 ` [PULL 12/16] i386/tdx: Fix build on 32-bit host Paolo Bonzini
2025-06-03 21:45 ` [PULL 13/16] i386/tdvf: " Paolo Bonzini
2025-06-03 21:45 ` [PULL 14/16] rust: add "bits", a custom bitflags implementation Paolo Bonzini
2025-06-03 21:45 ` [PULL 15/16] rust: pl011: use the bits macro Paolo Bonzini
2025-06-03 21:45 ` [PULL 16/16] rust: qemu-api-macros: add from_bits and into_bits to #[derive(TryInto)] Paolo Bonzini
2025-06-05 14:56 ` [PULL 00/16] rust, i386 changes for 2025-06-03 Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250603214523.131185-7-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).