qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, mst@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCHv3 0/2] pci: allow PCI bus slots to be marked as reserved
Date: Mon, 4 Sep 2017 12:50:31 +0300	[thread overview]
Message-ID: <8901c7e1-76f8-ff0e-c4e3-70b35e609e77@redhat.com> (raw)
In-Reply-To: <be3aee2e-bfa0-b18c-f14f-eff2224b7d03@ilande.co.uk>

On 31/08/2017 9:54, Mark Cave-Ayland wrote:
> On 16/07/17 21:27, Mark Cave-Ayland wrote:
> 
>> For some machines it is impossible to plug devices into a particular PCI bus
>> slot, e.g. for a real Ultra 5 there are 2 PCI bridges attached to the root
>> bus behind which all devices must be plugged. Ignoring this rule will cause
>> problems with interrupt routing since the interrupt numbers are calculated
>> based upon PCI bridge id and secondary PCI bus slot id.
>>
>> This patchset adds a new slot_reserved_mask property to PCIBus which is a
>> bitmask used to indicate whether PCI bus slots are reserved, i.e. they cannot
>> be used for hot or cold plugging on a particular PCI bus.
>>
>> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>>
>> v3:
>> - Rebase onto master
>> - Simplify pci_bus_devfn_available() as suggested by Marcel
>> - Also simplify pci_bus_devfn_reserved() in a similar manner
>>
>> v2:
>> - Rename dev_reserved_mask to slot_reserved_mask as suggested by Marcel
>> - Squash patches 2 and 3 together
>>
>>
>> Mark Cave-Ayland (2):
>>    pci: move check for existing devfn into new pci_bus_devfn_available()
>>      helper
>>    pci: add reserved slot check to do_pci_register_device()
>>
>>   hw/pci/pci.c             |   26 ++++++++++++++++++++++----
>>   include/hw/pci/pci_bus.h |    1 +
>>   2 files changed, 23 insertions(+), 4 deletions(-)
> 
> Ping? Is there any chance to get this in soon, as I ended up having to
> drop a couple of sun4u patch series for 2.10 that were dependent upon
> this :(
> 
> I have R-B tags from Marcel, however my understanding is that this patch
> still needs review from Michael?
> 

Hi Mark,
I think Michael did not start yet to pick patches for 2.11 .

Thanks,
Marcel

> Here is the link to the patch that depends upon this:
> https://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg03041.html
> 
> 
> Many thanks,
> 
> Mark.
> 

      reply	other threads:[~2017-09-04  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16 20:27 [Qemu-devel] [PATCHv3 0/2] pci: allow PCI bus slots to be marked as reserved Mark Cave-Ayland
2017-07-16 20:27 ` [Qemu-devel] [PATCHv3 1/2] pci: move check for existing devfn into new pci_bus_devfn_available() helper Mark Cave-Ayland
2017-07-17  8:21   ` Marcel Apfelbaum
2017-09-04 10:01   ` Yi Min Zhao
2017-09-06 19:02     ` Mark Cave-Ayland
2017-07-16 20:27 ` [Qemu-devel] [PATCHv3 2/2] pci: add reserved slot check to do_pci_register_device() Mark Cave-Ayland
2017-07-17  8:23   ` Marcel Apfelbaum
2017-08-31  6:54 ` [Qemu-devel] [PATCHv3 0/2] pci: allow PCI bus slots to be marked as reserved Mark Cave-Ayland
2017-09-04  9:50   ` Marcel Apfelbaum [this message]

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=8901c7e1-76f8-ff0e-c4e3-70b35e609e77@redhat.com \
    --to=marcel@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mst@redhat.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 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).