From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Elena Afanasova <eafanasova@gmail.com>,
kvm@vger.kernel.org, stefanha@redhat.com, jag.raman@oracle.com,
elena.ufimtseva@oracle.com, pbonzini@redhat.com, mst@redhat.com,
cohuck@redhat.com, john.levon@nutanix.com
Subject: Re: [RFC v3 1/5] KVM: add initial support for KVM_SET_IOREGION
Date: Mon, 22 Mar 2021 09:57:55 +0000 [thread overview]
Message-ID: <YFhqI8TalF+hrITi@stefanha-x1.localdomain> (raw)
In-Reply-To: <41e24c31-8742-099d-5011-9b762faa8670@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
On Tue, Mar 09, 2021 at 01:26:48PM +0800, Jason Wang wrote:
> On 2021/2/21 8:04 下午, Elena Afanasova wrote:
> > @@ -1308,6 +1332,7 @@ struct kvm_vfio_spapr_tce {
> > struct kvm_userspace_memory_region)
> > #define KVM_SET_TSS_ADDR _IO(KVMIO, 0x47)
> > #define KVM_SET_IDENTITY_MAP_ADDR _IOW(KVMIO, 0x48, __u64)
> > +#define KVM_SET_IOREGION _IOW(KVMIO, 0x49, struct kvm_ioregion)
>
>
> I wonder how could we extend ioregion fd in the future? Do we need something
> like handshake or version here?
The struct kvm_ioregion->flags field can be used to enable optional
features. KVM capabilities can be used to test the presence of optional
features. This might be enough.
A different approach to extensibility is a sizeof(struct kvm_ioregion)
field for arbitrary extensions to the struct.
> > +static int
> > +kvm_set_ioregion(struct kvm *kvm, struct kvm_ioregion *args)
> > +{
> > + int ret;
> > +
> > + enum kvm_bus bus_idx = get_bus_from_flags(args->flags);
> > +
> > + /* check for range overflow */
> > + if (args->guest_paddr + args->memory_size < args->guest_paddr)
> > + return -EINVAL;
> > + /* If size is ignored only posted writes are allowed */
> > + if (!args->memory_size && !(args->flags & KVM_IOREGION_POSTED_WRITES))
>
>
> We don't have flags like KVM_IOREGION_POSTED_WRITES for ioeventfd. Is this a
> must?
There is no way to trigger a FAST_MMIO read. Guest accesses, including
memory loads, appear as writes.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-22 9:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 12:04 [RFC v3 0/5] Introduce MMIO/PIO dispatch file descriptors (ioregionfd) Elena Afanasova
2021-02-21 12:04 ` [RFC v3 1/5] KVM: add initial support for KVM_SET_IOREGION Elena Afanasova
2021-02-24 10:06 ` Stefan Hajnoczi
2021-03-05 13:09 ` Cornelia Huck
2021-03-09 5:26 ` Jason Wang
2021-03-22 9:57 ` Stefan Hajnoczi [this message]
2021-02-21 12:04 ` [RFC v3 2/5] KVM: x86: add support for ioregionfd signal handling Elena Afanasova
2021-02-24 10:42 ` Stefan Hajnoczi
2021-03-09 5:51 ` Jason Wang
2021-03-17 14:19 ` Elena Afanasova
2021-03-26 6:00 ` Jason Wang
2021-02-21 12:04 ` [RFC v3 3/5] KVM: implement wire protocol Elena Afanasova
2021-02-24 11:02 ` Stefan Hajnoczi
2021-03-09 6:19 ` Jason Wang
2021-03-17 13:08 ` Elena Afanasova
2021-03-26 6:21 ` Jason Wang
2021-03-29 16:17 ` Stefan Hajnoczi
2021-02-21 12:04 ` [RFC v3 4/5] KVM: add ioregionfd context Elena Afanasova
2021-02-24 11:27 ` Stefan Hajnoczi
2021-03-09 7:54 ` Jason Wang
2021-03-09 8:01 ` Paolo Bonzini
2021-03-10 13:20 ` Elena Afanasova
2021-03-10 14:11 ` Paolo Bonzini
2021-03-10 16:41 ` Elena Afanasova
[not found] ` <6ff79d0b-3b6a-73d3-ffbd-e4af9758735f@redhat.com>
2021-03-17 10:46 ` Elena Afanasova
2021-03-26 6:47 ` Jason Wang
2021-02-21 12:04 ` [RFC v3 5/5] KVM: enforce NR_IOBUS_DEVS limit if kmemcg is disabled Elena Afanasova
2021-02-21 17:06 ` [RFC v3 0/5] Introduce MMIO/PIO dispatch file descriptors (ioregionfd) Paolo Bonzini
2021-02-22 16:40 ` Elena Afanasova
2021-02-24 11:34 ` 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=YFhqI8TalF+hrITi@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=cohuck@redhat.com \
--cc=eafanasova@gmail.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=jasowang@redhat.com \
--cc=john.levon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.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).