qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Zihan Yang <whois.zihan.yang@gmail.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC v4 3/6] i386/acpi-build: describe new pci domain in AML
Date: Sat, 25 Aug 2018 22:58:46 +0300	[thread overview]
Message-ID: <f7926420-ccd7-6821-f18d-794eb3a96105@gmail.com> (raw)
In-Reply-To: <CAKwiv-gVDxJWm4Oc+sSmsfdawLoo0F8L5n6xMznk9ixkCLR0yA@mail.gmail.com>



On 08/19/2018 05:00 AM, Zihan Yang wrote:
> Marcel Apfelbaum <marcel.apfelbaum@gmail.com> 于2018年8月18日周六 上午1:49写道:
>>
>>
>> On 08/09/2018 09:34 AM, Zihan Yang wrote:
>>> Describe new pci segments of host bridges in AML as new pci devices,
>>> with _SEG and _BBN to let them be in DSDT.
>>>
>>> Besides, bus_nr indicates the bus number of pxb-pcie under pcie.0 bus,
>>> but since we put it into separate domain, it should be zero,
>> Why should it be 0? Isn't possible we start another domain from bus_nr> 0?
> In the last version, I got a misunderstanding about bus_nr, and you pointed me
> out that we should start from bus 0 when in new domain. I can support this
> start_bus in later patch, but I wonder when would we want to start a domain
> from bus_nr > 0? I'm not quite familiar with the use case.

That is a good point. I can't think of a reason to start a new PCI
domain with a bus number  >0 , but is it possible.
So if it doesn't complicate the implementation we don't
want this kind of limitation.
On the other hand, if it makes the code too complicated,
we can argue for requiring it.


Thanks,
Marcel

[...]

  reply	other threads:[~2018-08-25 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09  6:34 [Qemu-devel] [RFC v4 3/6] i386/acpi-build: describe new pci domain in AML Zihan Yang
2018-08-17 17:49 ` Marcel Apfelbaum
2018-08-19  2:00   ` Zihan Yang
2018-08-25 19:58     ` Marcel Apfelbaum [this message]
2018-08-27  2:19       ` Zihan Yang

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=f7926420-ccd7-6821-f18d-794eb3a96105@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=whois.zihan.yang@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).