qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	Aleksandr Bezzubikov <zuban32s@gmail.com>,
	seabios@seabios.org, Laszlo Ersek <lersek@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] [RFC PATCH 0/2] Allow RedHat PCI bridges reserve more buses than necessary during init
Date: Fri, 21 Jul 2017 21:21:08 +0300	[thread overview]
Message-ID: <510a9fe7-2a38-f8c4-caa6-27c2805890c1@redhat.com> (raw)
In-Reply-To: <20170721172843.GA6606@morn.lan>

On 21/07/2017 20:28, Kevin O'Connor wrote:
> On Fri, Jul 21, 2017 at 03:15:46PM +0300, Marcel Apfelbaum wrote:
>> On 21/07/2017 13:04, Gerd Hoffmann wrote:
>>> I'd prefer to have a single vendor capability for all resource
>>> allocation hints provided by qemu.
>> Sure, the capability looking something like:
>>
>>     [flags: reserve-buses|reserve-IO|reserve-MEM|...]
>>     [extra-buses][IO-size][MEM-size]
>>
>>     if reserve-buses -> use 'extra-buses' value and so on
> 
> I don't have any objection to using a PCI capability, but I do wonder
> if fw_cfg would be a better fit.  This information is purely qemu ->
> firmware, right?
> 

Hi Kevin,

Right, but theoretically speaking a guest OS driver could also
get the hint on hotplug, or simply because the OS chooses to re-assign
resources on its own.

A while ago we discussed the fw_cfg option, but Gerd preferred
the vendor capability, and since the capability looked cleaner
Aleksandr opted for it.

He will send V2 soon together with the QEMU counterpart feature.

Thanks,
Marcel

> -Kevin
> 

  reply	other threads:[~2017-07-21 18:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 13:20 [Qemu-devel] [RFC PATCH 0/2] Allow RedHat PCI bridges reserve more buses than necessary during init Aleksandr Bezzubikov
2017-07-19 13:20 ` [Qemu-devel] [RFC PATCH 1/2] pci: add support for direct usage of bdf for capability lookup Aleksandr Bezzubikov
2017-07-19 14:24   ` Marcel Apfelbaum
2017-07-19 13:20 ` [Qemu-devel] [RFC PATCH 2/2] pci: enable RedHat pci bridges to reserve more buses Aleksandr Bezzubikov
2017-07-19 13:56   ` Konrad Rzeszutek Wilk
2017-07-19 14:30     ` Marcel Apfelbaum
2017-07-19 13:57 ` [Qemu-devel] [RFC PATCH 0/2] Allow RedHat PCI bridges reserve more buses than necessary during init Konrad Rzeszutek Wilk
2017-07-19 17:14   ` Alexander Bezzubikov
2017-07-19 18:18     ` Konrad Rzeszutek Wilk
     [not found]       ` <CAKSfGUCp=AFDjm24bMOpaSAA5FiDZXO0ZrBvuCp4wT+5EbhqDA@mail.gmail.com>
2017-07-19 18:38         ` [Qemu-devel] Fwd: " Alexander Bezzubikov
2017-07-19 18:56           ` Konrad Rzeszutek Wilk
2017-07-19 19:37             ` Marcel Apfelbaum
2017-07-20  6:52 ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2017-07-21  8:19   ` Marcel Apfelbaum
2017-07-21 10:04     ` Gerd Hoffmann
2017-07-21 12:15       ` Marcel Apfelbaum
2017-07-21 12:42         ` Gerd Hoffmann
2017-07-21 13:40           ` Marcel Apfelbaum
2017-07-24  8:41             ` Gerd Hoffmann
2017-07-21 17:28         ` Kevin O'Connor
2017-07-21 18:21           ` Marcel Apfelbaum [this message]
2017-07-24  8:39           ` Gerd Hoffmann

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=510a9fe7-2a38-f8c4-caa6-27c2805890c1@redhat.com \
    --to=marcel@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    --cc=zuban32s@gmail.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).