From: "Michael S. Tsirkin" <mst@redhat.com> To: Parav Pandit <parav@nvidia.com> Cc: "virtio-dev@lists.oasis-open.org" <virtio-dev@lists.oasis-open.org>, "cohuck@redhat.com" <cohuck@redhat.com>, "virtio-comment@lists.oasis-open.org" <virtio-comment@lists.oasis-open.org>, Shahaf Shuler <shahafs@nvidia.com> Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH 00/11] Introduce transitional mmr pci device Date: Mon, 3 Apr 2023 13:16:32 -0400 [thread overview] Message-ID: <20230403130950-mutt-send-email-mst@kernel.org> (raw) In-Reply-To: <PH0PR12MB54813E4193BC32775BDB2019DC929@PH0PR12MB5481.namprd12.prod.outlook.com> On Mon, Apr 03, 2023 at 03:36:25PM +0000, Parav Pandit wrote: > > > > From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis- > > open.org> On Behalf Of Michael S. Tsirkin > > > > Transport vq for legacy MMR purpose seems fine with its latency and DMA > > overheads. > > > Your question was about "scalability". > > > After your latest response, I am unclear what "scalability" means. > > > Do you mean saving the register space in the PCI device? > > > > yes that's how you used scalability in the past. > > > Ok. I am aligned. > > > > If yes, than, no for legacy guests for scalability it is not required, because the > > legacy register is subset of 1.x. > > > > Weird. what does guest being legacy have to do with a wish to save registers > > on the host hardware? > Because legacy has subset of the registers of 1.x. So no new registers additional expected on legacy side. > > > You don't have so many legacy guests as modern > > guests? Why? > > > This isn't true. > > There is a trade-off, upto certain N, MMR based register access is fine. > This is because 1.x is exposing super set of registers of legacy. > Beyond a certain point device will have difficulty in doing MMR for legacy and 1.x. > At that point, legacy over tvq can be better scale but with lot higher latency order of magnitude higher compare to MMR. > If tvq being the only transport for these registers access, it would hurt at lower scale too, due the primary nature of non_register access. > And scale is relative from device to device. Wow! Why an order of magnitide? > > > > > > > > > And presumably it can all be done in firmware ... > > > > > > Is there actual hardware that can't implement transport vq but > > > > > > is going to implement the mmr spec? > > > > > > > > > > > Nvidia and Marvell DPUs implement MMR spec. > > > > > > > > Hmm implement it in what sense exactly? > > > > > > > Do not follow the question. > > > The proposed series will be implemented as PCI SR-IOV devices using MMR > > spec. > > > > > > > > Transport VQ has very high latency and DMA overheads for 2 to 4 > > > > > bytes > > > > read/write. > > > > > > > > How many of these 2 byte accesses trigger from a typical guest? > > > > > > > Mostly during the VM boot time. 20 to 40 registers read write access. > > > > That is not a lot! How long does a DMA operation take then? > > > > > > > And before discussing "why not that approach", lets finish > > > > > reviewing "this > > > > approach" first. > > > > > > > > That's a weird way to put it. We don't want so many ways to do > > > > legacy if we can help it. > > > Sure, so lets finish the review of current proposal details. > > > At the moment > > > a. I don't see any visible gain of transport VQ other than device reset part I > > explained. > > > > For example, we do not need a new range of device IDs and existing drivers can > > bind on the host. > > > So, unlikely due to already discussed limitation of feature negotiation. > Existing transitional driver would also look for an IOBAR being second limitation. Some confusion here. If you have a transitional driver you do not need a legacy device. > > > b. it can be a way with high latency, DMA overheads on the virtqueue for > > read/writes for small access. > > > > numbers? > It depends on the implementation, but at minimum, writes and reads can pay order of magnitude higher in 10 msec range. A single VQ roundtrip takes a minimum of 10 milliseconds? This is indeed completely unworkable for transport vq. Points: - even for memory mapped you have an access take 1 millisecond? Extremely slow. Why? - Why is DMA 10x more expensive? I expect it to be 2x more expensive: Normal read goes cpu -> device -> cpu, DMA does cpu -> device -> memory -> device -> cpu Reason I am asking is because it is important for transport vq to have a workable design. But let me guess. Is there a chance that you are talking about an interrupt driven design? *That* is going to be slow though I don't think 10msec, more like 10usec. But I expect transport vq to typically work by (adaptive?) polling mostly avoiding interrupts. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com> To: Parav Pandit <parav@nvidia.com> Cc: "virtio-dev@lists.oasis-open.org" <virtio-dev@lists.oasis-open.org>, "cohuck@redhat.com" <cohuck@redhat.com>, "virtio-comment@lists.oasis-open.org" <virtio-comment@lists.oasis-open.org>, Shahaf Shuler <shahafs@nvidia.com> Subject: Re: [virtio-comment] Re: [PATCH 00/11] Introduce transitional mmr pci device Date: Mon, 3 Apr 2023 13:16:32 -0400 [thread overview] Message-ID: <20230403130950-mutt-send-email-mst@kernel.org> (raw) In-Reply-To: <PH0PR12MB54813E4193BC32775BDB2019DC929@PH0PR12MB5481.namprd12.prod.outlook.com> On Mon, Apr 03, 2023 at 03:36:25PM +0000, Parav Pandit wrote: > > > > From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis- > > open.org> On Behalf Of Michael S. Tsirkin > > > > Transport vq for legacy MMR purpose seems fine with its latency and DMA > > overheads. > > > Your question was about "scalability". > > > After your latest response, I am unclear what "scalability" means. > > > Do you mean saving the register space in the PCI device? > > > > yes that's how you used scalability in the past. > > > Ok. I am aligned. > > > > If yes, than, no for legacy guests for scalability it is not required, because the > > legacy register is subset of 1.x. > > > > Weird. what does guest being legacy have to do with a wish to save registers > > on the host hardware? > Because legacy has subset of the registers of 1.x. So no new registers additional expected on legacy side. > > > You don't have so many legacy guests as modern > > guests? Why? > > > This isn't true. > > There is a trade-off, upto certain N, MMR based register access is fine. > This is because 1.x is exposing super set of registers of legacy. > Beyond a certain point device will have difficulty in doing MMR for legacy and 1.x. > At that point, legacy over tvq can be better scale but with lot higher latency order of magnitude higher compare to MMR. > If tvq being the only transport for these registers access, it would hurt at lower scale too, due the primary nature of non_register access. > And scale is relative from device to device. Wow! Why an order of magnitide? > > > > > > > > > And presumably it can all be done in firmware ... > > > > > > Is there actual hardware that can't implement transport vq but > > > > > > is going to implement the mmr spec? > > > > > > > > > > > Nvidia and Marvell DPUs implement MMR spec. > > > > > > > > Hmm implement it in what sense exactly? > > > > > > > Do not follow the question. > > > The proposed series will be implemented as PCI SR-IOV devices using MMR > > spec. > > > > > > > > Transport VQ has very high latency and DMA overheads for 2 to 4 > > > > > bytes > > > > read/write. > > > > > > > > How many of these 2 byte accesses trigger from a typical guest? > > > > > > > Mostly during the VM boot time. 20 to 40 registers read write access. > > > > That is not a lot! How long does a DMA operation take then? > > > > > > > And before discussing "why not that approach", lets finish > > > > > reviewing "this > > > > approach" first. > > > > > > > > That's a weird way to put it. We don't want so many ways to do > > > > legacy if we can help it. > > > Sure, so lets finish the review of current proposal details. > > > At the moment > > > a. I don't see any visible gain of transport VQ other than device reset part I > > explained. > > > > For example, we do not need a new range of device IDs and existing drivers can > > bind on the host. > > > So, unlikely due to already discussed limitation of feature negotiation. > Existing transitional driver would also look for an IOBAR being second limitation. Some confusion here. If you have a transitional driver you do not need a legacy device. > > > b. it can be a way with high latency, DMA overheads on the virtqueue for > > read/writes for small access. > > > > numbers? > It depends on the implementation, but at minimum, writes and reads can pay order of magnitude higher in 10 msec range. A single VQ roundtrip takes a minimum of 10 milliseconds? This is indeed completely unworkable for transport vq. Points: - even for memory mapped you have an access take 1 millisecond? Extremely slow. Why? - Why is DMA 10x more expensive? I expect it to be 2x more expensive: Normal read goes cpu -> device -> cpu, DMA does cpu -> device -> memory -> device -> cpu Reason I am asking is because it is important for transport vq to have a workable design. But let me guess. Is there a chance that you are talking about an interrupt driven design? *That* is going to be slow though I don't think 10msec, more like 10usec. But I expect transport vq to typically work by (adaptive?) polling mostly avoiding interrupts. -- MST This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-04-03 17:16 UTC|newest] Thread overview: 399+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-30 22:58 [virtio-dev] [PATCH 00/11] Introduce transitional mmr pci device Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-30 22:58 ` [virtio-dev] [PATCH 01/11] transport-pci: Use lowecase alphabets Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-30 22:58 ` [virtio-dev] [PATCH 02/11] transport-pci: Move transitional device id to legacy section Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-31 6:43 ` [virtio-dev] " Michael S. Tsirkin 2023-03-31 6:43 ` [virtio-comment] " Michael S. Tsirkin 2023-03-31 21:24 ` [virtio-dev] " Parav Pandit 2023-03-31 21:24 ` [virtio-comment] " Parav Pandit 2023-04-02 7:54 ` [virtio-dev] " Michael S. Tsirkin 2023-04-02 7:54 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 14:42 ` [virtio-dev] " Parav Pandit 2023-04-03 14:42 ` [virtio-comment] " Parav Pandit 2023-04-03 14:50 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 14:50 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 14:58 ` [virtio-dev] " Parav Pandit 2023-04-03 14:58 ` [virtio-comment] " Parav Pandit 2023-04-03 15:14 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 15:14 ` [virtio-comment] " Michael S. Tsirkin 2023-03-30 22:58 ` [virtio-dev] [PATCH 03/11] transport-pci: Split notes of PCI Device Layout Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-30 22:58 ` [virtio-dev] [PATCH 04/11] transport-pci: Rename and move legacy PCI Device layout section Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-30 22:58 ` [virtio-dev] [PATCH 05/11] introduction: Add missing helping verb Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-30 22:58 ` [virtio-dev] [PATCH 06/11] introduction: Introduce transitional MMR interface Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-04-07 9:17 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 9:17 ` [virtio-comment] " Michael S. Tsirkin 2023-03-30 22:58 ` [virtio-dev] [PATCH 07/11] transport-pci: Introduce transitional MMR device id Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-04-04 7:28 ` [virtio-dev] " Michael S. Tsirkin 2023-04-04 7:28 ` [virtio-comment] " Michael S. Tsirkin 2023-04-04 16:08 ` [virtio-dev] " Parav Pandit 2023-04-04 16:08 ` [virtio-comment] " Parav Pandit 2023-04-07 12:03 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 12:03 ` Michael S. Tsirkin 2023-04-07 15:18 ` Parav Pandit 2023-04-07 15:18 ` [virtio-dev] " Parav Pandit 2023-04-07 15:51 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 15:51 ` Michael S. Tsirkin 2023-04-09 3:15 ` [virtio-dev] " Parav Pandit 2023-04-09 3:15 ` Parav Pandit 2023-04-10 10:18 ` [virtio-dev] " Michael S. Tsirkin 2023-04-10 10:18 ` Michael S. Tsirkin 2023-04-10 14:34 ` [virtio-dev] " Parav Pandit 2023-04-10 14:34 ` Parav Pandit 2023-04-10 19:58 ` [virtio-dev] " Michael S. Tsirkin 2023-04-10 19:58 ` Michael S. Tsirkin 2023-04-10 20:16 ` [virtio-dev] " Parav Pandit 2023-04-10 20:16 ` Parav Pandit 2023-04-07 8:37 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 8:37 ` [virtio-comment] " Michael S. Tsirkin 2023-03-30 22:58 ` [virtio-dev] [PATCH 08/11] transport-pci: Introduce virtio extended capability Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-04-04 7:35 ` [virtio-dev] " Michael S. Tsirkin 2023-04-04 7:35 ` [virtio-comment] " Michael S. Tsirkin 2023-04-04 7:54 ` [virtio-dev] " Cornelia Huck 2023-04-04 7:54 ` [virtio-comment] " Cornelia Huck 2023-04-04 12:43 ` [virtio-dev] " Michael S. Tsirkin 2023-04-04 12:43 ` [virtio-comment] " Michael S. Tsirkin 2023-04-04 13:19 ` [virtio-dev] " Cornelia Huck 2023-04-04 13:19 ` [virtio-comment] " Cornelia Huck 2023-04-04 14:37 ` [virtio-dev] " Michael S. Tsirkin 2023-04-04 14:37 ` [virtio-comment] " Michael S. Tsirkin 2023-04-10 16:21 ` [virtio-dev] " Parav Pandit 2023-04-10 16:21 ` [virtio-comment] " Parav Pandit 2023-04-10 19:49 ` [virtio-dev] " Michael S. Tsirkin 2023-04-10 19:49 ` [virtio-comment] " Michael S. Tsirkin 2023-04-10 19:57 ` [virtio-dev] " Parav Pandit 2023-04-10 19:57 ` [virtio-comment] " Parav Pandit 2023-04-10 20:02 ` [virtio-dev] " Michael S. Tsirkin 2023-04-10 20:02 ` [virtio-comment] " Michael S. Tsirkin 2023-04-11 8:39 ` [virtio-dev] " Cornelia Huck 2023-04-11 8:39 ` [virtio-comment] " Cornelia Huck 2023-04-04 21:18 ` [virtio-dev] " Parav Pandit 2023-04-04 21:18 ` [virtio-comment] " Parav Pandit 2023-04-05 5:10 ` [virtio-dev] " Michael S. Tsirkin 2023-04-05 5:10 ` [virtio-comment] " Michael S. Tsirkin 2023-04-05 13:16 ` [virtio-dev] " Parav Pandit 2023-04-05 13:16 ` [virtio-comment] " Parav Pandit 2023-04-07 8:15 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 8:15 ` [virtio-comment] " Michael S. Tsirkin 2023-04-10 1:36 ` [virtio-dev] " Jason Wang 2023-04-10 1:36 ` [virtio-comment] " Jason Wang 2023-04-10 6:24 ` Michael S. Tsirkin 2023-04-10 6:24 ` [virtio-comment] " Michael S. Tsirkin 2023-04-10 7:16 ` Jason Wang 2023-04-10 7:16 ` [virtio-comment] " Jason Wang 2023-04-10 10:04 ` Michael S. Tsirkin 2023-04-10 10:04 ` [virtio-comment] " Michael S. Tsirkin 2023-04-11 2:19 ` Jason Wang 2023-04-11 2:19 ` [virtio-comment] " Jason Wang 2023-04-11 7:00 ` Michael S. Tsirkin 2023-04-11 7:00 ` [virtio-comment] " Michael S. Tsirkin 2023-04-11 9:07 ` Jason Wang 2023-04-11 9:07 ` [virtio-comment] " Jason Wang 2023-04-11 10:43 ` Michael S. Tsirkin 2023-04-11 10:43 ` [virtio-comment] " Michael S. Tsirkin 2023-04-11 13:59 ` Parav Pandit 2023-04-11 13:59 ` [virtio-comment] " Parav Pandit 2023-04-11 14:11 ` Michael S. Tsirkin 2023-04-11 14:11 ` [virtio-comment] " Michael S. Tsirkin 2023-04-11 13:47 ` Parav Pandit 2023-04-11 13:47 ` [virtio-comment] " Parav Pandit 2023-04-11 14:02 ` Michael S. Tsirkin 2023-04-11 14:02 ` [virtio-comment] " Michael S. Tsirkin 2023-04-11 14:07 ` [virtio-dev] " Parav Pandit 2023-04-11 14:07 ` Parav Pandit 2023-04-11 14:10 ` [virtio-dev] " Michael S. Tsirkin 2023-04-11 14:10 ` Michael S. Tsirkin 2023-04-11 14:30 ` [virtio-dev] " Parav Pandit 2023-04-11 14:30 ` Parav Pandit 2023-04-10 17:54 ` Parav Pandit 2023-04-10 17:54 ` [virtio-comment] " Parav Pandit 2023-04-10 17:58 ` [virtio-dev] " Parav Pandit 2023-04-10 17:58 ` Parav Pandit 2023-04-11 3:28 ` Jason Wang 2023-04-11 3:28 ` [virtio-comment] " Jason Wang 2023-04-11 19:01 ` Parav Pandit 2023-04-11 19:01 ` [virtio-comment] " Parav Pandit 2023-04-11 21:25 ` Michael S. Tsirkin 2023-04-11 21:25 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 0:40 ` Parav Pandit 2023-04-12 0:40 ` [virtio-comment] " Parav Pandit 2023-04-12 2:56 ` Michael S. Tsirkin 2023-04-12 2:56 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 4:07 ` Jason Wang 2023-04-12 4:07 ` [virtio-comment] " Jason Wang 2023-04-12 4:20 ` Michael S. Tsirkin 2023-04-12 4:20 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 4:53 ` [virtio-dev] " Jason Wang 2023-04-12 4:53 ` Jason Wang 2023-04-12 5:25 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 5:25 ` Michael S. Tsirkin 2023-04-12 5:37 ` [virtio-dev] " Jason Wang 2023-04-12 5:37 ` Jason Wang 2023-04-13 17:03 ` [virtio-dev] " Michael S. Tsirkin 2023-04-13 17:03 ` Michael S. Tsirkin 2023-04-12 4:04 ` Jason Wang 2023-04-12 4:04 ` [virtio-comment] " Jason Wang 2023-04-12 4:13 ` Parav Pandit 2023-04-12 4:13 ` [virtio-comment] " Parav Pandit 2023-04-12 4:20 ` Michael S. Tsirkin 2023-04-12 4:20 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 4:55 ` Jason Wang 2023-04-12 4:55 ` [virtio-comment] " Jason Wang 2023-05-19 6:10 ` [virtio-dev] " Michael S. Tsirkin 2023-05-19 6:10 ` [virtio-comment] " Michael S. Tsirkin 2023-05-19 21:02 ` [virtio-dev] " Parav Pandit 2023-05-19 21:02 ` [virtio-comment] " Parav Pandit 2023-05-21 5:57 ` [virtio-dev] " Michael S. Tsirkin 2023-05-21 5:57 ` [virtio-comment] " Michael S. Tsirkin 2023-05-21 13:24 ` [virtio-dev] " Parav Pandit 2023-05-21 13:24 ` [virtio-comment] " Parav Pandit 2023-05-21 14:34 ` [virtio-dev] " Michael S. Tsirkin 2023-05-21 14:34 ` [virtio-comment] " Michael S. Tsirkin 2023-03-30 22:58 ` [virtio-dev] [PATCH 09/11] transport-pci: Describe PCI MMR dev config registers Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-04-07 8:55 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 8:55 ` [virtio-comment] " Michael S. Tsirkin 2023-04-10 1:33 ` Jason Wang 2023-04-10 1:33 ` [virtio-dev] " Jason Wang 2023-04-10 6:14 ` Michael S. Tsirkin 2023-04-10 6:14 ` Michael S. Tsirkin 2023-04-10 6:20 ` [virtio-dev] " Jason Wang 2023-04-10 6:20 ` Jason Wang 2023-04-10 6:39 ` [virtio-dev] " Michael S. Tsirkin 2023-04-10 6:39 ` Michael S. Tsirkin 2023-04-10 7:20 ` [virtio-dev] " Jason Wang 2023-04-10 7:20 ` Jason Wang 2023-04-10 10:06 ` [virtio-dev] " Michael S. Tsirkin 2023-04-10 10:06 ` Michael S. Tsirkin 2023-04-11 2:13 ` [virtio-dev] " Jason Wang 2023-04-11 2:13 ` Jason Wang 2023-04-11 7:04 ` [virtio-dev] " Michael S. Tsirkin 2023-04-11 7:04 ` Michael S. Tsirkin 2023-04-11 9:01 ` [virtio-dev] " Jason Wang 2023-04-11 9:01 ` Jason Wang [not found] ` <CALBs2cXURMEzCGnULicXbsBfwnKE5cZOz=M-_hhFCXZ=Lqb9Nw@mail.gmail.com> 2023-04-11 10:39 ` [virtio-dev] " Michael S. Tsirkin 2023-04-11 10:39 ` Michael S. Tsirkin 2023-04-11 11:03 ` [virtio-dev] " Yan Vugenfirer 2023-04-11 10:42 ` Michael S. Tsirkin 2023-04-11 10:42 ` Michael S. Tsirkin 2023-04-12 3:58 ` [virtio-dev] " Jason Wang 2023-04-12 3:58 ` Jason Wang 2023-04-12 4:15 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 4:15 ` Michael S. Tsirkin 2023-04-12 4:51 ` [virtio-dev] " Jason Wang 2023-04-12 4:51 ` Jason Wang 2023-04-12 5:01 ` [virtio-dev] " Parav Pandit 2023-04-12 5:01 ` Parav Pandit 2023-04-12 5:14 ` [virtio-dev] " Jason Wang 2023-04-12 5:14 ` Jason Wang 2023-04-12 5:30 ` [virtio-dev] " Parav Pandit 2023-04-12 5:30 ` Parav Pandit 2023-04-12 5:38 ` [virtio-dev] " Jason Wang 2023-04-12 5:38 ` Jason Wang 2023-04-12 5:55 ` [virtio-dev] " Parav Pandit 2023-04-12 5:55 ` Parav Pandit 2023-04-12 6:15 ` [virtio-dev] " Jason Wang 2023-04-12 6:15 ` Jason Wang 2023-04-12 14:23 ` [virtio-dev] " Parav Pandit 2023-04-12 14:23 ` Parav Pandit 2023-04-13 1:48 ` [virtio-dev] " Jason Wang 2023-04-13 1:48 ` Jason Wang 2023-04-13 3:31 ` [virtio-dev] " Parav Pandit 2023-04-13 3:31 ` Parav Pandit 2023-04-13 5:14 ` [virtio-dev] " Jason Wang 2023-04-13 5:14 ` Jason Wang 2023-04-13 17:19 ` [virtio-dev] " Michael S. Tsirkin 2023-04-13 17:19 ` Michael S. Tsirkin 2023-04-13 19:39 ` [virtio-dev] " Parav Pandit 2023-04-13 19:39 ` Parav Pandit 2023-04-14 3:09 ` [virtio-dev] " Jason Wang 2023-04-14 3:09 ` Jason Wang 2023-04-14 3:18 ` [virtio-dev] " Parav Pandit 2023-04-14 3:18 ` Parav Pandit 2023-04-14 3:37 ` [virtio-dev] " Jason Wang 2023-04-14 3:37 ` Jason Wang 2023-04-14 3:51 ` [virtio-dev] " Parav Pandit 2023-04-14 3:51 ` Parav Pandit 2023-04-14 7:05 ` [virtio-dev] " Michael S. Tsirkin 2023-04-14 7:05 ` Michael S. Tsirkin 2023-04-17 3:22 ` [virtio-dev] " Jason Wang 2023-04-17 3:22 ` Jason Wang 2023-04-17 17:23 ` [virtio-dev] " Parav Pandit 2023-04-17 17:23 ` Parav Pandit 2023-04-17 20:26 ` [virtio-dev] " Michael S. Tsirkin 2023-04-17 20:26 ` Michael S. Tsirkin 2023-04-17 20:28 ` [virtio-dev] " Parav Pandit 2023-04-17 20:28 ` Parav Pandit 2023-04-18 0:36 ` [virtio-dev] " Jason Wang 2023-04-18 0:36 ` Jason Wang 2023-04-18 1:30 ` [virtio-dev] " Parav Pandit 2023-04-18 1:30 ` Parav Pandit 2023-04-18 11:58 ` [virtio-dev] " Michael S. Tsirkin 2023-04-18 11:58 ` Michael S. Tsirkin 2023-04-18 12:09 ` [virtio-dev] " Parav Pandit 2023-04-18 12:09 ` Parav Pandit 2023-04-18 12:30 ` [virtio-dev] " Michael S. Tsirkin 2023-04-18 12:30 ` Michael S. Tsirkin 2023-04-18 12:36 ` [virtio-dev] " Parav Pandit 2023-04-18 12:36 ` Parav Pandit 2023-04-18 1:01 ` Jason Wang 2023-04-18 1:01 ` [virtio-dev] " Jason Wang 2023-04-18 1:48 ` [virtio-dev] " Parav Pandit 2023-04-18 1:48 ` Parav Pandit 2023-04-13 17:24 ` [virtio-dev] " Parav Pandit 2023-04-13 17:24 ` Parav Pandit 2023-04-13 21:02 ` [virtio-dev] " Michael S. Tsirkin 2023-04-13 21:02 ` Michael S. Tsirkin 2023-04-13 21:08 ` [virtio-dev] " Parav Pandit 2023-04-13 21:08 ` Parav Pandit 2023-04-14 2:36 ` [virtio-dev] " Jason Wang 2023-04-14 2:36 ` Jason Wang 2023-04-14 2:43 ` [virtio-dev] " Parav Pandit 2023-04-14 2:43 ` Parav Pandit 2023-04-14 6:57 ` [virtio-dev] " Michael S. Tsirkin 2023-04-14 6:57 ` Michael S. Tsirkin 2023-04-16 13:41 ` Parav Pandit 2023-04-16 13:41 ` [virtio-dev] " Parav Pandit 2023-04-16 20:44 ` [virtio-dev] " Michael S. Tsirkin 2023-04-16 20:44 ` Michael S. Tsirkin 2023-04-17 16:59 ` [virtio-dev] " Parav Pandit 2023-04-17 16:59 ` Parav Pandit 2023-04-18 1:09 ` [virtio-dev] " Jason Wang 2023-04-18 1:09 ` Jason Wang 2023-04-18 1:37 ` [virtio-dev] " Parav Pandit 2023-04-18 1:37 ` Parav Pandit 2023-04-14 6:58 ` [virtio-dev] " Michael S. Tsirkin 2023-04-14 6:58 ` Michael S. Tsirkin 2023-04-14 3:08 ` [virtio-dev] " Jason Wang 2023-04-14 3:08 ` Jason Wang 2023-04-14 3:13 ` [virtio-dev] " Parav Pandit 2023-04-14 3:13 ` Parav Pandit 2023-04-14 3:18 ` [virtio-dev] " Jason Wang 2023-04-14 3:18 ` Jason Wang 2023-04-14 3:22 ` [virtio-dev] " Parav Pandit 2023-04-14 3:22 ` Parav Pandit 2023-04-14 3:29 ` [virtio-dev] " Jason Wang 2023-04-14 3:29 ` Jason Wang 2023-04-11 13:57 ` [virtio-dev] " Parav Pandit 2023-04-11 13:57 ` Parav Pandit 2023-04-12 4:33 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 4:33 ` [virtio-comment] " Michael S. Tsirkin 2023-03-30 22:58 ` [virtio-dev] [PATCH 10/11] transport-pci: Use driver notification PCI capability Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-04-12 4:31 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 4:31 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 4:37 ` [virtio-dev] " Parav Pandit 2023-04-12 4:37 ` [virtio-comment] " Parav Pandit 2023-04-12 4:43 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 4:43 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 4:48 ` [virtio-dev] " Parav Pandit 2023-04-12 4:48 ` [virtio-comment] " Parav Pandit 2023-04-12 5:02 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 5:02 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 5:06 ` [virtio-dev] " Parav Pandit 2023-04-12 5:06 ` Parav Pandit 2023-04-12 5:17 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 5:17 ` Michael S. Tsirkin 2023-04-12 5:24 ` [virtio-dev] " Parav Pandit 2023-04-12 5:24 ` Parav Pandit 2023-04-12 5:27 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 5:27 ` Michael S. Tsirkin 2023-03-30 22:58 ` [virtio-dev] [PATCH 11/11] conformance: Add transitional MMR interface conformance Parav Pandit 2023-03-30 22:58 ` [virtio-comment] " Parav Pandit 2023-03-31 7:03 ` [virtio-dev] Re: [PATCH 00/11] Introduce transitional mmr pci device Michael S. Tsirkin 2023-03-31 7:03 ` [virtio-comment] " Michael S. Tsirkin 2023-03-31 21:43 ` [virtio-dev] " Parav Pandit 2023-03-31 21:43 ` [virtio-comment] " Parav Pandit 2023-04-03 14:53 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 14:53 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 14:57 ` [virtio-dev] " Parav Pandit 2023-04-03 14:57 ` [virtio-comment] " Parav Pandit 2023-04-03 15:06 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 15:06 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 15:16 ` [virtio-dev] " Parav Pandit 2023-04-03 15:16 ` [virtio-comment] " Parav Pandit 2023-04-03 15:23 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 15:23 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 15:34 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 15:34 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 15:47 ` [virtio-dev] " Parav Pandit 2023-04-03 15:47 ` [virtio-comment] " Parav Pandit 2023-04-03 17:28 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 17:28 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 17:35 ` [virtio-dev] " Parav Pandit 2023-04-03 17:35 ` [virtio-comment] " Parav Pandit 2023-04-03 17:39 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 17:39 ` [virtio-comment] " Michael S. Tsirkin 2023-04-03 15:36 ` [virtio-dev] " Parav Pandit 2023-04-03 15:36 ` Parav Pandit 2023-04-03 17:16 ` Michael S. Tsirkin [this message] 2023-04-03 17:16 ` Michael S. Tsirkin 2023-04-03 17:29 ` [virtio-dev] " Parav Pandit 2023-04-03 17:29 ` Parav Pandit 2023-04-03 18:02 ` Michael S. Tsirkin 2023-04-03 18:02 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 20:25 ` [virtio-dev] " Parav Pandit 2023-04-03 20:25 ` Parav Pandit 2023-04-03 21:04 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 21:04 ` Michael S. Tsirkin 2023-04-03 22:00 ` [virtio-dev] " Parav Pandit 2023-04-03 22:00 ` Parav Pandit 2023-04-07 9:35 ` [virtio-dev] " Michael S. Tsirkin 2023-04-07 9:35 ` Michael S. Tsirkin 2023-04-10 1:52 ` [virtio-dev] " Jason Wang 2023-04-10 1:52 ` Jason Wang 2023-04-03 14:45 ` [virtio-dev] Re: [virtio-comment] " Stefan Hajnoczi 2023-04-03 14:45 ` Stefan Hajnoczi 2023-04-03 14:53 ` [virtio-dev] " Parav Pandit 2023-04-03 14:53 ` Parav Pandit 2023-04-03 17:48 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 17:48 ` Michael S. Tsirkin 2023-04-03 19:11 ` [virtio-dev] " Stefan Hajnoczi 2023-04-03 19:11 ` Stefan Hajnoczi 2023-04-03 20:03 ` Michael S. Tsirkin 2023-04-03 20:03 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 19:48 ` [virtio-dev] " Parav Pandit 2023-04-03 19:48 ` Parav Pandit 2023-04-03 20:02 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 20:02 ` Michael S. Tsirkin 2023-04-03 20:42 ` [virtio-dev] " Parav Pandit 2023-04-03 20:42 ` Parav Pandit 2023-04-03 21:14 ` [virtio-dev] " Michael S. Tsirkin 2023-04-03 21:14 ` Michael S. Tsirkin 2023-04-03 22:08 ` [virtio-dev] " Parav Pandit 2023-04-03 22:08 ` Parav Pandit 2023-04-03 19:10 ` [virtio-dev] " Stefan Hajnoczi 2023-04-03 19:10 ` Stefan Hajnoczi 2023-04-03 20:27 ` Parav Pandit 2023-04-03 20:27 ` [virtio-dev] " Parav Pandit 2023-04-04 14:30 ` [virtio-dev] " Stefan Hajnoczi 2023-04-04 14:30 ` Stefan Hajnoczi 2023-04-12 4:48 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 4:48 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 4:52 ` [virtio-dev] " Parav Pandit 2023-04-12 4:52 ` [virtio-comment] " Parav Pandit 2023-04-12 5:12 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 5:12 ` [virtio-comment] " Michael S. Tsirkin 2023-04-12 5:15 ` [virtio-dev] " Parav Pandit 2023-04-12 5:15 ` Parav Pandit 2023-04-12 5:23 ` [virtio-dev] " Michael S. Tsirkin 2023-04-12 5:23 ` Michael S. Tsirkin 2023-04-12 5:39 ` [virtio-dev] " Parav Pandit 2023-04-12 5:39 ` Parav Pandit 2023-04-12 6:02 ` [virtio-dev] " Parav Pandit 2023-04-12 6:02 ` Parav Pandit 2023-04-12 5:10 ` [virtio-dev] " Halil Pasic 2023-04-12 5:10 ` [virtio-comment] " Halil Pasic 2023-04-25 2:42 ` [virtio-dev] " Parav Pandit 2023-04-25 2:42 ` [virtio-comment] " Parav Pandit 2023-05-02 7:17 ` [virtio-dev] " David Edmondson 2023-05-02 7:17 ` David Edmondson 2023-05-02 13:54 ` [virtio-dev] " Parav Pandit 2023-05-02 13:54 ` Parav Pandit
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=20230403130950-mutt-send-email-mst@kernel.org \ --to=mst@redhat.com \ --cc=cohuck@redhat.com \ --cc=parav@nvidia.com \ --cc=shahafs@nvidia.com \ --cc=virtio-comment@lists.oasis-open.org \ --cc=virtio-dev@lists.oasis-open.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: 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.