All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: Akihiko Odaki <akihiko.odaki@daynix.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Julia Suvorova <jusual@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PATCH v6 5/5] hw/pci: ensure PCIE devices are plugged into only slot 0 of PCIE port
Date: Fri, 30 Jun 2023 06:00:26 -0400	[thread overview]
Message-ID: <20230630055717-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <49B901C6-4819-4A00-8225-39FAA6678F3E@redhat.com>

On Fri, Jun 30, 2023 at 02:52:52PM +0530, Ani Sinha wrote:
> 
> 
> > On 30-Jun-2023, at 2:13 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > 
> > On Fri, Jun 30, 2023 at 02:06:59PM +0530, Ani Sinha wrote:
> >> 
> >> 
> >>> On 30-Jun-2023, at 2:02 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> >>> 
> >>> On Fri, Jun 30, 2023 at 01:11:33PM +0530, Ani Sinha wrote:
> >>>>> 
> >>>>> Thus the check for unoccupied function 0 needs to use pci_is_vf() instead of checking ARI capability, and that can happen in do_pci_register_device().
> >>>>> 
> >>>>>> Also where do you propose we move the check?
> >>>>> 
> >>>>> In pci_qdev_realize(), somewhere after pc->realize() and before option ROM loading.
> >>>> 
> >>>> Hmm, I tried this. The issue here is something like this would be now allowed since the PF has ARI capability:
> >>>> 
> >>>> -device pcie-root-port,id=p -device igb,bus=p,addr=0x2.0x0
> >>>> 
> >>>> The above should not be allowed and when used, we do not see the igb ethernet device from the guest OS.
> >>> 
> >>> I think it's allowed because it expects you to hotplug function 0 later,
> >> 
> >> This is about the igb device being plugged into the non-zero slot of the pci-root-port. The guest OS ignores it.
> > 
> > yes but if you later add a device with ARI and with next field pointing
> > slot 2 guest will suddently find both.
> 
> Hmm, I tried this:
> 
> -device pcie-root-port,id=p \
> -device igb,bus=p,addr=0x2.0x0 \
> -device igb,bus=p,addr=0x0.0x0 \
> 
> The guest only found the second igb device not the first. You can try too.

Because next parameter in pcie_ari_init does not match.


> > 
> >>> no?
> >>> 
> >>> I am quite worried about all this work going into blocking
> >>> what we think is disallowed configurations. We should have
> >>> maybe blocked them originally, but now that we didn't
> >>> there's a non zero chance of regressions,
> >> 
> >> Sigh,
> > 
> > There's value in patches 1-4 I think - the last patch helped you find
> > these. so there's value in this work.
> > 
> >> no medals here for being brave :-)
> > 
> > Try removing support for a 3.5mm jack next. Oh wait ...
> 
> Indeed. Everyone uses bluetooth these days. I for one is happy that the jack is gone (and they were bold enough to do it while Samsung and others still carry the useless port ) :-)
>  
> > 
> >>> and the benefit
> >>> is not guaranteed.
> >>> 
> >>> -- 
> >>> MST



  reply	other threads:[~2023-06-30 10:01 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  4:07 [PATCH v6 0/5] test and QEMU fixes to ensure proper PCIE device usage Ani Sinha
2023-06-29  4:07 ` [PATCH v6 1/5] tests/acpi: allow changes in DSDT.noacpihp table blob Ani Sinha
2023-06-29  4:07 ` [PATCH v6 2/5] tests/acpi/bios-tables-test: use the correct slot on the pcie-root-port Ani Sinha
2023-06-29  4:07 ` [PATCH v6 3/5] tests/acpi/bios-tables-test: update acpi blob q35/DSDT.noacpihp Ani Sinha
2023-06-29  4:07 ` [PATCH v6 4/5] tests/qtest/hd-geo-test: fix incorrect pcie-root-port usage and simplify test Ani Sinha
2023-06-29  7:03   ` Thomas Huth
2023-06-30  9:09   ` Igor Mammedov
2023-06-29  4:07 ` [PATCH v6 5/5] hw/pci: ensure PCIE devices are plugged into only slot 0 of PCIE port Ani Sinha
2023-06-29  6:47   ` Akihiko Odaki
2023-06-29  8:05     ` Ani Sinha
2023-06-29  8:49       ` Akihiko Odaki
2023-06-29 14:18         ` Ani Sinha
2023-06-30  2:43           ` Akihiko Odaki
2023-06-30  6:02             ` Michael S. Tsirkin
2023-06-30  7:41             ` Ani Sinha
2023-06-30  8:32               ` Michael S. Tsirkin
2023-06-30  8:36                 ` Ani Sinha
2023-06-30  8:43                   ` Michael S. Tsirkin
2023-06-30  9:22                     ` Ani Sinha
2023-06-30 10:00                       ` Michael S. Tsirkin [this message]
2023-06-30 10:37                         ` Ani Sinha
2023-06-30 10:40                           ` Michael S. Tsirkin
2023-06-30 10:45                             ` Ani Sinha
2023-06-30 10:49                             ` Ani Sinha
2023-06-30 11:36                           ` Akihiko Odaki
2023-06-30 11:47                             ` Ani Sinha
2023-06-30 11:55                             ` Akihiko Odaki
2023-06-30 13:56                               ` Ani Sinha
2023-07-01  7:09                                 ` Akihiko Odaki
2023-07-02  4:59                                   ` Michael S. Tsirkin
2023-07-03  6:08                                     ` Ani Sinha
2023-07-04  5:01                                       ` Akihiko Odaki
2023-07-04  5:39                                         ` Ani Sinha
2023-07-04 10:33                                           ` Ani Sinha
2023-07-04 10:36                                             ` Michael S. Tsirkin
2023-07-04 11:10                                               ` Ani Sinha
2023-07-03 13:31                                     ` Ani Sinha
2023-06-30 15:29                             ` Michael S. Tsirkin
2023-07-01  7:28                               ` Akihiko Odaki
2023-07-04 11:38                                 ` Igor Mammedov
2023-07-04 11:50                                   ` Akihiko Odaki
2023-07-04 12:36                                     ` Igor Mammedov
2023-07-04 12:51                                       ` Akihiko Odaki
2023-07-04 14:03                                     ` Ani Sinha
2023-07-05  2:30                                       ` Akihiko Odaki
2023-06-30 10:25                       ` Michael S. Tsirkin
2023-06-29 14:24   ` Michael S. Tsirkin
2023-06-29 14:37     ` Ani Sinha
2023-06-29 15:32       ` Michael S. Tsirkin
2023-06-29 15:57         ` Ani Sinha
2023-06-29 16:45           ` Ani Sinha

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=20230630055717-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=anisinha@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jusual@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=qemu-devel@nongnu.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: link
Be 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.