From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: PCI: Fix bus address conversion (was Re: commit rules for common git tree)
Date: Mon, 4 Jan 2010 21:10:08 +0200 [thread overview]
Message-ID: <20100104191008.GB20721@redhat.com> (raw)
In-Reply-To: <f43fc5581001041104yda3c0b4s12dec4bf2da23d28@mail.gmail.com>
On Mon, Jan 04, 2010 at 07:04:38PM +0000, Blue Swirl wrote:
> On Mon, Jan 4, 2010 at 6:33 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> >> On Sun, Dec 27, 2009 at 05:01:38PM -0600, Anthony Liguori wrote:
> >> > Likewise, if you see a patch go in that you think would have benefited
> >> > from being on the list, point it out. People are reasonable and if you
> >> > have a good suggestion, they'll value your input and be likely to seek
> >> > it out in the future.
> >
> > Here is another patch that would have benefitted from review
> > before commit:
> >
> >> commit cf616802171905a9b6d087a69caa3b978b9cd741
> >> Author: Blue Swirl <blauwirbel@gmail.com>
> >> Date: Sun Dec 27 20:52:36 2009 +0000
> >>
> >> PCI: Fix bus address conversion
> >>
> >> Pass physical addresses to map functions instead of PCI bus addresses.
> >>
> >> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> >
> > and previous related patches. The issues here that I see are:
> >
> > - IMO mem_base should really be pci_bus_t, as pci address might be
> > 64 bit mapped into 32 bit target
> >
> > - I think pci to pci bridges need mem_base copied from parent to child,
> > this does not seem to be done?
> >
> > - map functions need to get pci_bus_t (for io), and now they get
> > a cpu address there. The real fix IMO is moving the mapping
> > to within pci.c. I think Avi had a patch to do this -
> > any objections to refreshing it?
> >
> > Blue Swirl, could you comment please?
>
> The issues you point out (which may well be valid) are not related to
> the change made by the patch and should be addressed by new patches.
Yes, there's no harm in fixing them separately. The point I was making
is it is better to post patches on list so issues can be pointed out and
discussed without the need to dig through git history.
> IIRC Avi promised to refresh his patch but never delivered. I think
> Paul also wanted that the bus translation would be handled in a more
> generic way (eliminate map functions).
I'd like to eliminate map functions as well. Do you have a link to the original patch
btw?
--
MST
next prev parent reply other threads:[~2010-01-04 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091227113732.GA3833@redhat.com>
[not found] ` <20091227203453.GA30873@volta.aurel32.net>
[not found] ` <20091227215023.GB3278@redhat.com>
[not found] ` <20091227222326.GA10602@hall.aurel32.net>
[not found] ` <20091227224021.GA3443@redhat.com>
[not found] ` <4B37E752.1020000@codemonkey.ws>
2010-01-04 18:33 ` [Qemu-devel] Re: PCI: Fix bus address conversion (was Re: commit rules for common git tree) Michael S. Tsirkin
2010-01-04 18:47 ` Aurelien Jarno
2010-01-04 19:01 ` Michael S. Tsirkin
2010-01-04 19:04 ` Blue Swirl
2010-01-04 19:10 ` Michael S. Tsirkin [this message]
2010-01-04 19:49 ` Blue Swirl
2010-01-04 19:57 ` Michael S. Tsirkin
2010-01-05 23:14 ` [Qemu-devel] Re: PCI: Fix bus address conversion Andreas Färber
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=20100104191008.GB20721@redhat.com \
--to=mst@redhat.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.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).