From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] [PATCH] [1/4] Add per guest pvr
Date: Wed, 30 Jan 2008 21:40:16 +0000 [thread overview]
Message-ID: <1201729216.10632.33.camel@basalt> (raw)
In-Reply-To: <1201696318462-git-send-email-ehrhardt@linux.vnet.ibm.com>
On Wed, 2008-01-30 at 15:18 -0600, Hollis Blanchard wrote:
>
> Anyways, this probably isn't worth spending too much time on now. The
> immediate need is for the TLB accessors, and I think we can base those
> on the PVR without a full multi-arch guest solution.
Forgot to explain...
It looks like arch->vcpu.pvr is totally uninitialized right now. (I'm
surprised the guest hasn't complained.) Instead of setting it from
userspace, could you send a patch that initializes it to the hardware's
PVR value? It's a simple patch, and you can use that to disambiguate the
TLB stuff in later patches.
We can discuss the best way to handle this long term, but right now I
think virtual IO is more important.
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2008-01-30 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 12:31 [kvm-ppc-devel] [PATCH] [1/4] Add per guest pvr ehrhardt
2008-01-30 21:18 ` Hollis Blanchard
2008-01-30 21:40 ` Hollis Blanchard [this message]
2008-01-31 8:37 ` Christian Ehrhardt
2008-01-31 14:56 ` ehrhardt
2008-02-01 13:31 ` Zhang Wei
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=1201729216.10632.33.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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.