From: Pierre Morel <pmorel@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>,
Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] s390x/pci: let pci devices start in configured mode
Date: Wed, 8 Nov 2017 10:19:48 +0100 [thread overview]
Message-ID: <7a5497d4-f8eb-e1ae-bc42-3a5afaa1b750@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171108095314.7687676e.cohuck@redhat.com>
On 08/11/2017 09:53, Cornelia Huck wrote:
> On Tue, 7 Nov 2017 18:54:55 +0100
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
>> Currently, to enable a pci device in the guest, the user has to issue
>> echo 1 > /sys/bus/pci/slots/00000000/power. This is not what people
>> expect. On an LPAR, the user can put a PCI device in configured or
>> deconfigured state via IOCDS. The "start in deconfigured state" can be
>> used for "sharing" a pci function across LPARs. This is not what we are
>> going to use in KVM, so always start configured.
>>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Acked-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
>> Reviewed-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
>> ---
>> hw/s390x/s390-pci-bus.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
>> index e7a58e8..2b1e140 100644
>> --- a/hw/s390x/s390-pci-bus.c
>> +++ b/hw/s390x/s390-pci-bus.c
>> @@ -715,7 +715,7 @@ static void s390_pcihost_hot_plug(HotplugHandler *hotplug_dev,
>> pbdev->pdev = pdev;
>> pbdev->iommu = s390_pci_get_iommu(s, pdev->bus, pdev->devfn);
>> pbdev->iommu->pbdev = pbdev;
>> - pbdev->state = ZPCI_FS_STANDBY;
>> + pbdev->state = ZPCI_FS_DISABLED;
>>
>> if (s390_pci_msix_init(pbdev)) {
>> error_setg(errp, "MSI-X support is mandatory "
>
> A pci function already has to be configured before we can assign it via
> vfio, right?
Yes it is right, otherwise we do not see the PCI device in the sysfs and
we can not provide it to QEMU.
Regards
Pierre
>
> I think I'll queue this for 2.11.
>
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
next prev parent reply other threads:[~2017-11-08 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 17:54 [Qemu-devel] [PATCH 0/1] s390/pci more enhancements Christian Borntraeger
2017-11-07 17:54 ` [Qemu-devel] [PATCH 1/1] s390x/pci: let pci devices start in configured mode Christian Borntraeger
2017-11-08 8:53 ` Cornelia Huck
2017-11-08 9:19 ` Pierre Morel [this message]
2017-11-08 11:05 ` Cornelia Huck
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=7a5497d4-f8eb-e1ae-bc42-3a5afaa1b750@linux.vnet.ibm.com \
--to=pmorel@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=zyimin@linux.vnet.ibm.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).