From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Wadim Mueller <wafgo01@gmail.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Shunsuke Mie" <mie@igel.co.jp>,
linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/3] Add support for Block Passthrough Endpoint function driver
Date: Wed, 25 Sep 2024 11:23:36 +0200 [thread overview]
Message-ID: <20240925092336.mf6plixpqe7fcsoa@thinkpad> (raw)
In-Reply-To: <rq85odwmqryrr4.fsf@gmail.com>
On Mon, Feb 26, 2024 at 07:47:30PM +0100, Wadim Mueller wrote:
[...]
> Okay, I understand this. The hypervisor was more of an example. I will
> try to explain.
>
> I am currently reading through the virtio spec [1].
> In chapter 4.1.4.5.1 there is the following statement:
>
> "The device MUST reset ISR status to 0 on driver read."
>
> So I was wondering, how we, as an PCI EP Device, supposed to clear a
> register when the driver reads the same register? I mean how do we detect a
> register read?
> If you are a hypervisor its easy to do so, because you can intercept
> every memory access made my the guest (the same applies if you build
> custom HW for this purpose). But for us as an EP device its
> difficult to detect this, even with MSIs and Doorbell Registers in
> place.
>
Sorry for not responding earlier. Conversation got lost.
Yes, I do agree that some of the expecatations of the current Virtio spec cannot
be satisfied by the physical endpoint device. So I presented some of these
problems at this year plumbers and the Virtio maintainer in the room agreed to
have changes in the spec to fix these issues.
But it is not clear atm on whether we should introduce the changes in the
virtio-pci transport or introduce a new transport altogether. I can include you
in the discussions if you are still interested.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-09-25 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 21:03 [PATCH 0/3] Add support for Block Passthrough Endpoint function driver Wadim Mueller
2024-02-24 21:04 ` [PATCH 1/3] PCI: Add PCI Endpoint function driver for Block-device passthrough Wadim Mueller
2024-02-24 21:04 ` [PATCH 2/3] PCI: Add PCI driver for a PCI EP remote Blockdevice Wadim Mueller
2024-02-24 21:04 ` [PATCH 3/3] Documentation: PCI: Add documentation for the PCI Block Passthrough Wadim Mueller
2024-02-25 16:09 ` [PATCH 0/3] Add support for Block Passthrough Endpoint function driver Manivannan Sadhasivam
2024-02-25 20:39 ` Wadim Mueller
2024-02-26 9:45 ` Manivannan Sadhasivam
2024-02-26 12:58 ` Damien Le Moal
2024-02-26 18:47 ` Wadim Mueller
2024-09-25 9:23 ` Manivannan Sadhasivam [this message]
2024-02-26 16:47 ` Frank Li
2024-02-26 11:08 ` Christoph Hellwig
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=20240925092336.mf6plixpqe7fcsoa@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mie@igel.co.jp \
--cc=wafgo01@gmail.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).