From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH V2] booke_206_tlbwe: Discard invalid bits in MAS2
Date: Fri, 25 May 2012 03:38:07 +0200 [thread overview]
Message-ID: <4FBEE27F.7050304@suse.de> (raw)
In-Reply-To: <26C5B5DB-E18C-45A5-B54F-FCB2928C7708@suse.de>
Am 21.05.2012 21:24, schrieb Alexander Graf:
>
> On 21.05.2012, at 18:31, Andreas Färber <afaerber@suse.de> wrote:
>
>> [...] I believe
>> op_helper.c is dropped in Blue's AREG0 conversion, so I would recommend
>> to rebase on that, since rebasing the large code movements was kind of
>> nasty. Now that we've fixed ppc and ppc64 TCG it could be applied to
>> ppc-next, no?
>
> Good point. Blue, mind to resend? :)
I managed to rebase my copy of Blue's ppc series onto qom-next but ran
into bisectability issues. So I've rebased your branch (qemu.areg0)
instead and pushed it for you to reset ppc-next to:
http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/ppc
This is based on current qom-next; the only conflicts were due to
removal of cpu_state_reset() and return type change of cpu_ppc_init().
Rebased version compile-tested on x86 and ppc w/KVM, and lightly
runtime-tested by booting into openSUSE Factory .iso on -M pseries.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-05-25 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 16:11 [Qemu-devel] [PATCH V2] booke_206_tlbwe: Discard invalid bits in MAS2 Fabien Chouteau
2012-05-21 16:31 ` Andreas Färber
2012-05-21 19:24 ` Alexander Graf
2012-05-25 1:38 ` Andreas Färber [this message]
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=4FBEE27F.7050304@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--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 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).