From: malc <av1474@comtv.ru>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Applied PATCH] Split TLB addend and target_phys_addr_t
Date: Tue, 6 Apr 2010 02:44:09 +0400 (MSD) [thread overview]
Message-ID: <alpine.LNX.2.00.1004060242540.17170@linmac> (raw)
In-Reply-To: <3D8AED7A-94E9-4911-ABE1-0A09AFD325D5@suse.de>
On Mon, 5 Apr 2010, Alexander Graf wrote:
>
> On 05.04.2010, at 14:41, malc wrote:
>
> > On Mon, 5 Apr 2010, Paul Brook wrote:
> >
> >> I think I got all the tcg backend bits right, but can't test most of them. Please test and report any problems.
> >>
> >> Historically the qemu tlb "addend" field was used for both RAM and IO accesses,
> >> so needed to be able to hold both host addresses (unsigned long) and guest
> >> physical addresses (target_phys_addr_t). However since the introduction of
> >> the iotlb field it has only been used for RAM accesses.
> >>
> >> This means we can change the type of addend to unsigned long, and remove
> >> associated hacks in the big-endian TCG backends.
> >>
> >> We can also remove the host dependence from target_phys_addr_t.
> >>
> >> Signed-off-by: Paul Brook <paul@codesourcery.com>
> >
> > PPC32 seems to be operational.
> >
> > Alexander: Can you please test it a bit more thoroughly, my PPCs are a bit
> > on the slow side.
>
> Test what exactly? Booting random guests with TCG on PPC?
Booting 64 bit guests with 32 bit ppc hosts specifically.
[Testing whether 64bit host still works would be nice too, thanks]
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2010-04-05 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 1:21 [Qemu-devel] [Applied PATCH] Split TLB addend and target_phys_addr_t Paul Brook
2010-04-05 12:41 ` malc
2010-04-05 21:38 ` Alexander Graf
2010-04-05 22:44 ` malc [this message]
2010-04-07 15:09 ` Alexander Graf
2010-04-07 15:20 ` Alexander Graf
2010-04-07 16:32 ` malc
2010-04-07 16:40 ` Alexander Graf
2010-04-17 4:07 ` malc
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=alpine.LNX.2.00.1004060242540.17170@linmac \
--to=av1474@comtv.ru \
--cc=agraf@suse.de \
--cc=paul@codesourcery.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).