On Wed, Apr 12, 2023 at 01:37:59PM +0800, Jason Wang wrote:
> On Wed, Apr 12, 2023 at 1:25 PM Michael S. Tsirkin wrote:
> >
> > On Wed, Apr 12, 2023 at 12:53:52PM +0800, Jason Wang wrote:
> > > On Wed, Apr 12, 2023 at 12:20 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Wed, Apr 12, 2023
On Wed, Apr 12, 2023 at 1:25 PM Michael S. Tsirkin wrote:
>
> On Wed, Apr 12, 2023 at 12:53:52PM +0800, Jason Wang wrote:
> > On Wed, Apr 12, 2023 at 12:20 PM Michael S. Tsirkin wrote:
> > >
> > > On Wed, Apr 12, 2023 at 12:07:26PM +0800, Jason Wang wrote:
> > > > On Wed, Apr 12, 2023 at 5:25 AM
On Wed, Apr 12, 2023 at 12:53:52PM +0800, Jason Wang wrote:
> On Wed, Apr 12, 2023 at 12:20 PM Michael S. Tsirkin wrote:
> >
> > On Wed, Apr 12, 2023 at 12:07:26PM +0800, Jason Wang wrote:
> > > On Wed, Apr 12, 2023 at 5:25 AM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Tue, Apr 11, 2023
On Wed, Apr 12, 2023 at 12:21 PM Michael S. Tsirkin wrote:
>
> On Wed, Apr 12, 2023 at 12:04:45PM +0800, Jason Wang wrote:
> > On Wed, Apr 12, 2023 at 3:01 AM Parav Pandit wrote:
> > >
> > >
> > > > From: virtio-dev@lists.oasis-open.org
> > > > On
> > > > Behalf Of Jason Wang
> > > > Sent: Mond
On Wed, Apr 12, 2023 at 12:20 PM Michael S. Tsirkin wrote:
>
> On Wed, Apr 12, 2023 at 12:07:26PM +0800, Jason Wang wrote:
> > On Wed, Apr 12, 2023 at 5:25 AM Michael S. Tsirkin wrote:
> > >
> > > On Tue, Apr 11, 2023 at 07:01:16PM +, Parav Pandit wrote:
> > > >
> > > > > From: virtio-dev@lis
On Wed, Apr 12, 2023 at 12:04:45PM +0800, Jason Wang wrote:
> On Wed, Apr 12, 2023 at 3:01 AM Parav Pandit wrote:
> >
> >
> > > From: virtio-dev@lists.oasis-open.org On
> > > Behalf Of Jason Wang
> > > Sent: Monday, April 10, 2023 11:29 PM
> >
> > > > However, it is not backward compatible, if th
On Wed, Apr 12, 2023 at 12:07:26PM +0800, Jason Wang wrote:
> On Wed, Apr 12, 2023 at 5:25 AM Michael S. Tsirkin wrote:
> >
> > On Tue, Apr 11, 2023 at 07:01:16PM +, Parav Pandit wrote:
> > >
> > > > From: virtio-dev@lists.oasis-open.org
> > > > On
> > > > Behalf Of Jason Wang
> > > > Sent:
> From: Jason Wang
> Sent: Wednesday, April 12, 2023 12:05 AM
> > > It is kind of intended since it is only used for new PCI-E features:
> > >
> > New fields in new extended pci cap area is fine.
> > Migrating old fields to be present in the new extended pci cap, is not your
> intention. Right?
On Wed, Apr 12, 2023 at 5:25 AM Michael S. Tsirkin wrote:
>
> On Tue, Apr 11, 2023 at 07:01:16PM +, Parav Pandit wrote:
> >
> > > From: virtio-dev@lists.oasis-open.org On
> > > Behalf Of Jason Wang
> > > Sent: Monday, April 10, 2023 11:29 PM
> >
> > > > However, it is not backward compatible,
On Wed, Apr 12, 2023 at 3:01 AM Parav Pandit wrote:
>
>
> > From: virtio-dev@lists.oasis-open.org On
> > Behalf Of Jason Wang
> > Sent: Monday, April 10, 2023 11:29 PM
>
> > > However, it is not backward compatible, if the device place them in
> > > extended capability, it will not work.
> > >
>
On Wed, Apr 12, 2023 at 12:40:53AM +, Parav Pandit wrote:
> > From: Michael S. Tsirkin
> > Sent: Tuesday, April 11, 2023 5:25 PM
> >
> > On Tue, Apr 11, 2023 at 07:01:16PM +, Parav Pandit wrote:
> > >
> > > > From: virtio-dev@lists.oasis-open.org
> > > > On Behalf Of Jason Wang
> > > > S
> From: Michael S. Tsirkin
> Sent: Tuesday, April 11, 2023 5:25 PM
>
> On Tue, Apr 11, 2023 at 07:01:16PM +, Parav Pandit wrote:
> >
> > > From: virtio-dev@lists.oasis-open.org
> > > On Behalf Of Jason Wang
> > > Sent: Monday, April 10, 2023 11:29 PM
> >
> > > > However, it is not backward c
On Tue, Apr 11, 2023 at 07:01:16PM +, Parav Pandit wrote:
>
> > From: virtio-dev@lists.oasis-open.org On
> > Behalf Of Jason Wang
> > Sent: Monday, April 10, 2023 11:29 PM
>
> > > However, it is not backward compatible, if the device place them in
> > > extended capability, it will not work.
> From: virtio-dev@lists.oasis-open.org On
> Behalf Of Jason Wang
> Sent: Monday, April 10, 2023 11:29 PM
> > However, it is not backward compatible, if the device place them in
> > extended capability, it will not work.
> >
>
> It is kind of intended since it is only used for new PCI-E feature
> From: Michael S. Tsirkin
> Sent: Tuesday, April 11, 2023 10:10 AM
>
> well, of course, my question was for a new, future device, can we put all
> capabilities in the extended space? will we be able to teach bios to access
> these?
Cannot speak for BIOS vendors,
but from PCI spec side, the e
On Tue, Apr 11, 2023 at 05:07:11PM +0800, Jason Wang wrote:
> > now, imagine someone building a new device. if existing drivers are not
> > a concern, it is possible to move capabilities all to extended space. is
> > that possible while keeping the bios working?
>
> This is possible but I'm not su
On Tue, Apr 11, 2023 at 02:07:27PM +, Parav Pandit wrote:
>
>
> > From: virtio-comm...@lists.oasis-open.org > open.org> On Behalf Of Michael S. Tsirkin
>
> > > >
> > > > now, imagine someone building a new device. if existing drivers are
> > > > not a concern, it is possible to move capabil
> From: virtio-comm...@lists.oasis-open.org open.org> On Behalf Of Michael S. Tsirkin
> > >
> > > now, imagine someone building a new device. if existing drivers are
> > > not a concern, it is possible to move capabilities all to extended
> > > space. is that possible while keeping the bios wo
On Tue, Apr 11, 2023 at 09:47:50AM -0400, Parav Pandit wrote:
>
>
> On 4/11/2023 3:00 AM, Michael S. Tsirkin wrote:
>
> > > I meant, it depends on the capability semantics. Both PASID and legacy
> > > MMIO don't need to be accessed by BIOS. We can't change legacy BIOS to
> > > use legacy MMIO ba
> From: Jason Wang
> Sent: Tuesday, April 11, 2023 5:07 AM
> This is possible but I'm not sure it's worthwhile. What happens if the device
> puts all capabilities in the extended space but the bios can't scan there? We
> can
> place them at both but it then doesn't address the out of space iss
On 4/11/2023 3:00 AM, Michael S. Tsirkin wrote:
I meant, it depends on the capability semantics. Both PASID and legacy
MMIO don't need to be accessed by BIOS. We can't change legacy BIOS to
use legacy MMIO bars.
Thanks
makes sense.
now, imagine someone building a new device. if existing
On Tue, Apr 11, 2023 at 05:07:11PM +0800, Jason Wang wrote:
> On Tue, Apr 11, 2023 at 3:00 PM Michael S. Tsirkin wrote:
> >
> > On Tue, Apr 11, 2023 at 10:19:39AM +0800, Jason Wang wrote:
> > > On Mon, Apr 10, 2023 at 6:04 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Mon, Apr 10, 2023 a
On Tue, Apr 11, 2023 at 3:00 PM Michael S. Tsirkin wrote:
>
> On Tue, Apr 11, 2023 at 10:19:39AM +0800, Jason Wang wrote:
> > On Mon, Apr 10, 2023 at 6:04 PM Michael S. Tsirkin wrote:
> > >
> > > On Mon, Apr 10, 2023 at 03:16:46PM +0800, Jason Wang wrote:
> > > > On Mon, Apr 10, 2023 at 2:24 PM M
On Tue, Apr 11, 2023 at 10:19:39AM +0800, Jason Wang wrote:
> On Mon, Apr 10, 2023 at 6:04 PM Michael S. Tsirkin wrote:
> >
> > On Mon, Apr 10, 2023 at 03:16:46PM +0800, Jason Wang wrote:
> > > On Mon, Apr 10, 2023 at 2:24 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Mon, Apr 10, 2023 a
On Tue, Apr 11, 2023 at 1:54 AM Parav Pandit wrote:
>
> Hi Jason,
>
> On 4/9/2023 9:36 PM, Jason Wang wrote:
> > On Fri, Mar 31, 2023 at 7:00 AM Parav Pandit wrote:
> >>
> >> PCI device configuration space for capabilities is limited to only 192
> >> bytes shared by many PCI capabilities of gener
On Mon, Apr 10, 2023 at 6:04 PM Michael S. Tsirkin wrote:
>
> On Mon, Apr 10, 2023 at 03:16:46PM +0800, Jason Wang wrote:
> > On Mon, Apr 10, 2023 at 2:24 PM Michael S. Tsirkin wrote:
> > >
> > > On Mon, Apr 10, 2023 at 09:36:17AM +0800, Jason Wang wrote:
> > > > On Fri, Mar 31, 2023 at 7:00 AM P
> From: virtio-comm...@lists.oasis-open.org open.org> On Behalf Of Parav Pandit
> We may need it even sooner than this because the AQ patch is expanding the
> structure located in legacy area.
I mixed up the two structures. AQ related field expansion doesn’t need
capability expansion.
Sorry ab
Hi Jason,
On 4/9/2023 9:36 PM, Jason Wang wrote:
On Fri, Mar 31, 2023 at 7:00 AM Parav Pandit wrote:
PCI device configuration space for capabilities is limited to only 192
bytes shared by many PCI capabilities of generic PCI device and virtio
specific.
Hence, introduce virtio extended capabi
On Mon, Apr 10, 2023 at 03:16:46PM +0800, Jason Wang wrote:
> On Mon, Apr 10, 2023 at 2:24 PM Michael S. Tsirkin wrote:
> >
> > On Mon, Apr 10, 2023 at 09:36:17AM +0800, Jason Wang wrote:
> > > On Fri, Mar 31, 2023 at 7:00 AM Parav Pandit wrote:
> > > >
> > > > PCI device configuration space for
On Mon, Apr 10, 2023 at 2:24 PM Michael S. Tsirkin wrote:
>
> On Mon, Apr 10, 2023 at 09:36:17AM +0800, Jason Wang wrote:
> > On Fri, Mar 31, 2023 at 7:00 AM Parav Pandit wrote:
> > >
> > > PCI device configuration space for capabilities is limited to only 192
> > > bytes shared by many PCI capab
On Mon, Apr 10, 2023 at 09:36:17AM +0800, Jason Wang wrote:
> On Fri, Mar 31, 2023 at 7:00 AM Parav Pandit wrote:
> >
> > PCI device configuration space for capabilities is limited to only 192
> > bytes shared by many PCI capabilities of generic PCI device and virtio
> > specific.
> >
> > Hence, i
On Fri, Mar 31, 2023 at 7:00 AM Parav Pandit wrote:
>
> PCI device configuration space for capabilities is limited to only 192
> bytes shared by many PCI capabilities of generic PCI device and virtio
> specific.
>
> Hence, introduce virtio extended capability that uses PCI Express
> extended capab
PCI device configuration space for capabilities is limited to only 192
bytes shared by many PCI capabilities of generic PCI device and virtio
specific.
Hence, introduce virtio extended capability that uses PCI Express
extended capability.
Subsequent patch uses this virtio extended capability.
Co-
33 matches
Mail list logo
