From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 3/5] PPC: E500: Generate dt pci irq map dynamically
Date: Wed, 12 Dec 2012 18:33:40 -0600 [thread overview]
Message-ID: <1355358820.28445.21@snotra> (raw)
In-Reply-To: <A0E676CB-8B44-408A-9875-62561FAAA905@suse.de> (from agraf@suse.de on Wed Dec 12 18:28:02 2012)
On 12/12/2012 06:28:02 PM, Alexander Graf wrote:
>
> On 13.12.2012, at 01:20, Scott Wood wrote:
>
> > On 12/12/2012 06:04:11 PM, Alexander Graf wrote:
> >> We could call bus->map_irq(...) with an artificially created
> PCIDevice struct ;). But that's pretty hacky.
> >
> > If we do anything like that, it should probably be to iterate over
> the devices that actually exist and add interrupt-map entries only
> for those.
>
> Right. Though I'm not sure how pci hotplug slots would look like in
> that model. I don't think we have PCIDevice structs there yet, but we
> would still need to keep interrupt maps ready.
Note that if we did limit it to only devices that actually exist, we'd
be producing a smaller interrupt-map than would be found on real
hardware for targets like mpc8544ds, if the slots aren't fully
populated.
> >> So you're indicating you'd like the below patch?
> >
> > I think you pasted a bit more than one patch, but yes.
>
> Yikes. It's way past midnight after all :).
>
> You mean I messed up and pasted more than I wanted or that I should
> split the patch? :)
The former. :-)
> >> agraf@lychee:/home/agraf/release/qemu> git add hw/ppce500_pci.h
> >> agraf@lychee:/home/agraf/release/qemu> git diff HEAD
> >> agraf@lychee:/home/agraf/release/qemu> git diff HEAD | cat
> >
> > What does piping through cat get you?
>
> Piping through cat gets me that I don't get the patch in less, so I
> can easily copy&paste it from my terminal into the email client even
> though it's bigger than my terminal window. Also not using less means
> that formatting stays consistent.
Ah, forgot about git doing different things based on what stdout is.
-Scott
next prev parent reply other threads:[~2012-12-13 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 14:09 [Qemu-devel] [PATCH 0/5] PPC: e500: Enable more PCI slots for -M ppce500 Alexander Graf
2012-12-12 14:09 ` [Qemu-devel] [PATCH 1/5] PPC: E500: PCI: Make first slot qdev settable Alexander Graf
2012-12-12 14:09 ` [Qemu-devel] [PATCH 2/5] PPC: E500: PCI: Make IRQ calculation more generic Alexander Graf
2012-12-12 14:09 ` [Qemu-devel] [PATCH 3/5] PPC: E500: Generate dt pci irq map dynamically Alexander Graf
2012-12-12 18:40 ` [Qemu-devel] [Qemu-ppc] " Scott Wood
2012-12-12 23:38 ` Alexander Graf
2012-12-12 23:43 ` Scott Wood
2012-12-13 0:04 ` Alexander Graf
2012-12-13 0:20 ` Scott Wood
2012-12-13 0:28 ` Alexander Graf
2012-12-13 0:33 ` Scott Wood [this message]
2012-12-13 0:36 ` Alexander Graf
2012-12-12 14:09 ` [Qemu-devel] [PATCH 4/5] PPC: E500: Move PCI slot information into params Alexander Graf
2012-12-12 14:09 ` [Qemu-devel] [PATCH 5/5] PPC: E500plat: Make a lot of PCI slots available Alexander Graf
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=1355358820.28445.21@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.