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] [PATCHv2 0/2] pci: allow PCI bus slots to be marked as reserved
Date: Fri, 14 Jul 2017 13:25:46 +0300	[thread overview]
Message-ID: <2f0d3ed6-5aa3-851e-3e9f-c08532ca1120@redhat.com> (raw)
In-Reply-To: <6d3baced-070b-908a-95b0-7784e2f0ca4e@ilande.co.uk>

On 14/07/2017 12:59, Mark Cave-Ayland wrote:
> On 11/07/17 22:44, 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>
>>
>> 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             |   34 ++++++++++++++++++++++++++++++----
>>   include/hw/pci/pci_bus.h |    1 +
>>   2 files changed, 31 insertions(+), 4 deletions(-)
> 
> Ping? Any further feedback on the v2 version? My latest set of sun4u
> patches is dependent upon this patchset and it's freeze coming up next week!
> 

Hi,

As in prev version, other than the minor comment
on replacing "if (...) return true; else return false"
with the actual value, I am OK with it.

I believe Michael asked to see the series using this feature,
can you add a link to it, or post it with the dependency on this one?

Thanks,
Marcel

> 
> ATB,
> 
> Mark.
> 

  reply	other threads:[~2017-07-14 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 21:44 [Qemu-devel] [PATCHv2 0/2] pci: allow PCI bus slots to be marked as reserved Mark Cave-Ayland
2017-07-11 21:44 ` [Qemu-devel] [PATCHv2 1/2] pci: move check for existing devfn into new pci_bus_devfn_available() helper Mark Cave-Ayland
2017-07-11 21:44 ` [Qemu-devel] [PATCHv2 2/2] pci: add reserved slot check to do_pci_register_device() Mark Cave-Ayland
2017-07-14  9:59 ` [Qemu-devel] [PATCHv2 0/2] pci: allow PCI bus slots to be marked as reserved Mark Cave-Ayland
2017-07-14 10:25   ` Marcel Apfelbaum [this message]
2017-07-14 10:37     ` Mark Cave-Ayland
2017-07-16  7:28       ` Marcel Apfelbaum
2017-07-16 19:22         ` Mark Cave-Ayland

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=2f0d3ed6-5aa3-851e-3e9f-c08532ca1120@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).