From: David Gibson <david@gibson.dropbear.id.au>
To: Eric Blake <eblake@redhat.com>
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 1/1] spapr_pci: remove all child functions in function zero unplug
Date: Fri, 23 Aug 2019 15:29:03 +1000 [thread overview]
Message-ID: <20190823052903.GA3027@umbus.fritz.box> (raw)
In-Reply-To: <63a2fef4-3e9d-5dfc-9ccb-2924bb1fe808@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
On Thu, Aug 22, 2019 at 04:11:45PM -0500, Eric Blake wrote:
> On 8/22/19 2:59 PM, Daniel Henrique Barboza wrote:
> > There is nothing wrong with how sPAPR handles multifunction PCI
> > hot unplugs. The problem is that x86 does it simpler. Instead of
> > removing each non-zero function and then removing function zero,
> > x86 can remove any function of the slot to trigger the hot unplug.
> >
>
> > +++ b/hw/ppc/spapr_pci.c
> > @@ -1700,11 +1700,13 @@ static void spapr_pci_unplug_request(HotplugHandler *plug_handler,
> > state = func_drck->dr_entity_sense(func_drc);
> > if (state == SPAPR_DR_ENTITY_SENSE_PRESENT
> > && !spapr_drc_unplug_requested(func_drc)) {
> > - error_setg(errp,
> > - "PCI: slot %d, function %d still present. "
> > - "Must unplug all non-0 functions first.",
> > - slotnr, i);
> > - return;
> > + /*
> > + * Attempting to remove function 0 of a multifunction
> > + * device will will cascade into removing all child
> > + * functions, even if their unplug weren't requested
>
> s/weren't/wasn't/
Actually, I think this is technically a subjunctive, which would make
it "were" rather than "was". Modern English usage doesn't really do
the subjunctive, though.
</more-pedantic-than-thou>
With my maintainer hat on, rather than pedant hat, the meaning is
clear so I really don't care, especially from a contributer whose
first language isn't English.
>
> > + * beforehand.
> > + */
> > + spapr_drc_detach(func_drc);
> > }
> > }
> > }
> >
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-23 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 19:59 [Qemu-devel] [PATCH v1 1/1] spapr_pci: remove all child functions in function zero unplug Daniel Henrique Barboza
2019-08-22 21:11 ` Eric Blake
2019-08-23 5:29 ` David Gibson [this message]
2019-08-23 5:31 ` David Gibson
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=20190823052903.GA3027@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=danielhb413@gmail.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).