From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, junjie.mao@hotmail.com,
zhao1.liu@intel.com, qemu-rust@nongnu.org
Subject: Re: [PATCH 2/2] rust: add bindings for interrupt sources
Date: Fri, 22 Nov 2024 09:32:30 +0100 [thread overview]
Message-ID: <CABgObfbOj8FCvjXOM_AF8=jyFMi1bs-gfsRu+_GH3802hLhM1A@mail.gmail.com> (raw)
In-Reply-To: <70f44731-6879-4adf-a71b-a781af48fe99@linaro.org>
> > +/// Interrupt sources are used by devices to pass changes to a boolean value to
> > +/// other devices (typically interrupt or GPIO controllers). QEMU interrupt
> > +/// sources are always active-high.
>
> So 'always active-high' = true below? (Wondering about pulsation, if the
> true -> false transition is always correct).
Yeah, I mean that raise uses true (or 1 :)) and lower uses false.
an example?
> Is this deliberate to restrict the Rust binding to boolean? (Maybe you
> envision a VectoredInterruptSource implementation for that).
No, I simply wasn't aware of that. I'll adjust; do you have
an example?
> > +/// Interrupt sources can only be triggered under the Big QEMU Lock; they are
> > +/// neither `Send` nor `Sync`.
Oops, this is incorrect. BqlCell *is* Send/Sync, but checks the
BQL state at run-time.
Paolo
next prev parent reply other threads:[~2024-11-22 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 7:47 [PATCH 0/2] rust: safe wrappers for interrupt sources Paolo Bonzini
2024-11-22 7:47 ` [PATCH 1/2] rust: add BQL-enforcing Cell variant Paolo Bonzini
2024-11-26 14:56 ` Zhao Liu
2024-11-26 16:11 ` Paolo Bonzini
2024-11-27 6:35 ` Zhao Liu
2024-11-27 8:31 ` Paolo Bonzini
2024-11-27 6:54 ` Junjie Mao
2024-11-22 7:47 ` [PATCH 2/2] rust: add bindings for interrupt sources Paolo Bonzini
2024-11-22 8:28 ` Philippe Mathieu-Daudé
2024-11-22 8:32 ` Paolo Bonzini [this message]
2024-11-22 10:30 ` Philippe Mathieu-Daudé
2024-11-22 10:53 ` Paolo Bonzini
2024-11-22 11:07 ` Philippe Mathieu-Daudé
2024-11-26 13:45 ` Zhao Liu
2024-11-26 13:35 ` Paolo Bonzini
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='CABgObfbOj8FCvjXOM_AF8=jyFMi1bs-gfsRu+_GH3802hLhM1A@mail.gmail.com' \
--to=pbonzini@redhat.com \
--cc=junjie.mao@hotmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=zhao1.liu@intel.com \
/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).