From: Matthew Rosato <mjrosato@linux.ibm.com> To: Thomas Huth <thuth@redhat.com>, qemu-s390x@nongnu.org Cc: alex.williamson@redhat.com, schnelle@linux.ibm.com, cohuck@redhat.com, farman@linux.ibm.com, pmorel@linux.ibm.com, richard.henderson@linaro.org, david@redhat.com, pasic@linux.ibm.com, borntraeger@linux.ibm.com, mst@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org Subject: Re: [PATCH v2 0/9] s390x/pci: zPCI interpretation support Date: Tue, 18 Jan 2022 13:32:11 -0500 [thread overview] Message-ID: <c44a7ba3-37bf-6b25-1e89-719a1487ca20@linux.ibm.com> (raw) In-Reply-To: <32c83624-eb3b-05ea-6fb6-737bd9876db3@redhat.com> On 1/17/22 10:23 AM, Thomas Huth wrote: > On 14/01/2022 21.38, Matthew Rosato wrote: >> For QEMU, the majority of the work in enabling instruction interpretation >> is handled via new VFIO ioctls to SET the appropriate interpretation and >> interrupt forwarding modes, and to GET the function handle to use for >> interpretive execution. >> >> This series implements these new ioctls, as well as adding a new, >> optional >> 'intercept' parameter to zpci to request interpretation support not be >> used >> as well as an 'intassist' parameter to determine whether or not the >> firmware assist will be used for interrupt delivery or whether the host >> will be responsible for delivering all interrupts. > > Hi Matthew, > > would it make sense to create a docs/system/s390x/zpci.rst doc file, This is a good idea and probably something that was due for zpci before this series even. > too, where you could describe such new parameters like 'intassist' and > 'intercept' (or is it 'interp') ? ... otherwise hardly anybody except Oops, 'intercept' was a holdover from a previous version and effectively had an inverted meaning. It is indeed 'interp' with this current series (and subject to change again per other thread)
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Rosato <mjrosato@linux.ibm.com> To: Thomas Huth <thuth@redhat.com>, qemu-s390x@nongnu.org Cc: farman@linux.ibm.com, kvm@vger.kernel.org, pmorel@linux.ibm.com, schnelle@linux.ibm.com, cohuck@redhat.com, richard.henderson@linaro.org, qemu-devel@nongnu.org, pasic@linux.ibm.com, alex.williamson@redhat.com, mst@redhat.com, pbonzini@redhat.com, david@redhat.com, borntraeger@linux.ibm.com Subject: Re: [PATCH v2 0/9] s390x/pci: zPCI interpretation support Date: Tue, 18 Jan 2022 13:32:11 -0500 [thread overview] Message-ID: <c44a7ba3-37bf-6b25-1e89-719a1487ca20@linux.ibm.com> (raw) In-Reply-To: <32c83624-eb3b-05ea-6fb6-737bd9876db3@redhat.com> On 1/17/22 10:23 AM, Thomas Huth wrote: > On 14/01/2022 21.38, Matthew Rosato wrote: >> For QEMU, the majority of the work in enabling instruction interpretation >> is handled via new VFIO ioctls to SET the appropriate interpretation and >> interrupt forwarding modes, and to GET the function handle to use for >> interpretive execution. >> >> This series implements these new ioctls, as well as adding a new, >> optional >> 'intercept' parameter to zpci to request interpretation support not be >> used >> as well as an 'intassist' parameter to determine whether or not the >> firmware assist will be used for interrupt delivery or whether the host >> will be responsible for delivering all interrupts. > > Hi Matthew, > > would it make sense to create a docs/system/s390x/zpci.rst doc file, This is a good idea and probably something that was due for zpci before this series even. > too, where you could describe such new parameters like 'intassist' and > 'intercept' (or is it 'interp') ? ... otherwise hardly anybody except Oops, 'intercept' was a holdover from a previous version and effectively had an inverted meaning. It is indeed 'interp' with this current series (and subject to change again per other thread)
next prev parent reply other threads:[~2022-01-18 18:32 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 20:38 [PATCH v2 0/9] s390x/pci: zPCI interpretation support Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 1/9] Update linux headers Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 2/9] target/s390x: add zpci-interp to cpu models Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 3/9] fixup: force interp off for QEMU machine 6.2 and older Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 21:04 ` Matthew Rosato 2022-01-14 21:04 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 4/9] s390x/pci: enable for load/store intepretation Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-17 14:51 ` Thomas Huth 2022-01-17 14:51 ` Thomas Huth 2022-01-18 18:08 ` Matthew Rosato 2022-01-18 18:08 ` Matthew Rosato 2022-01-17 15:38 ` Thomas Huth 2022-01-17 15:38 ` Thomas Huth 2022-01-18 18:14 ` Matthew Rosato 2022-01-18 18:14 ` Matthew Rosato 2022-01-31 9:37 ` Pierre Morel 2022-01-31 9:37 ` Pierre Morel 2022-01-31 14:46 ` Pierre Morel 2022-01-31 17:11 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 5/9] s390x/pci: don't fence interpreted devices without MSI-X Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 6/9] s390x/pci: enable adapter event notification for interpreted devices Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-31 15:10 ` Pierre Morel 2022-01-31 15:10 ` Pierre Morel 2022-01-31 17:08 ` Matthew Rosato 2022-01-31 17:08 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 7/9] s390x/pci: use I/O Address Translation assist when interpreting Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 8/9] s390x/pci: use dtsm provided from vfio capabilities for interpreted devices Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-14 20:38 ` [PATCH v2 9/9] s390x/pci: let intercept devices have separate PCI groups Matthew Rosato 2022-01-14 20:38 ` Matthew Rosato 2022-01-17 15:23 ` [PATCH v2 0/9] s390x/pci: zPCI interpretation support Thomas Huth 2022-01-17 15:23 ` Thomas Huth 2022-01-18 18:32 ` Matthew Rosato [this message] 2022-01-18 18:32 ` Matthew Rosato 2022-02-04 12:39 ` Michael S. Tsirkin 2022-02-04 12:39 ` Michael S. Tsirkin
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=c44a7ba3-37bf-6b25-1e89-719a1487ca20@linux.ibm.com \ --to=mjrosato@linux.ibm.com \ --cc=alex.williamson@redhat.com \ --cc=borntraeger@linux.ibm.com \ --cc=cohuck@redhat.com \ --cc=david@redhat.com \ --cc=farman@linux.ibm.com \ --cc=kvm@vger.kernel.org \ --cc=mst@redhat.com \ --cc=pasic@linux.ibm.com \ --cc=pbonzini@redhat.com \ --cc=pmorel@linux.ibm.com \ --cc=qemu-devel@nongnu.org \ --cc=qemu-s390x@nongnu.org \ --cc=richard.henderson@linaro.org \ --cc=schnelle@linux.ibm.com \ --cc=thuth@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.