From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: RE: [PATCH 05 of 14] ppc: Create disassemble.h to extract
Date: Tue, 11 Nov 2008 14:56:20 +0000 [thread overview]
Message-ID: <1226415380.458.2.camel@localhost.localdomain> (raw)
In-Reply-To: <D8176E55B81822498D63816C4ADC70101B1CE4@zch01exm26.fsl.freescale.net>
On Tue, 2008-11-11 at 11:23 +0800, Liu Yu wrote:
> Since this header is created, will you consider to
> unify the argument list of kmppc_emul_tlbre/tlbwe/tlbsx, such as (struct
> kvm_vcpu *vcpu, u32 inst)?
>
>
> > -----Original Message-----
> > From: kvm-owner@vger.kernel.org
> > [mailto:kvm-owner@vger.kernel.org] On Behalf Of Hollis Blanchard
> > Sent: Wednesday, November 05, 2008 11:36 PM
> > To: avi@redhat.com
> > Cc: kvm@vger.kernel.org; kvm-ppc@vger.kernel.org
> > Subject: [PATCH 05 of 14] ppc: Create disassemble.h to
> > extract instructionfields
> >
> > This is used in a couple places in KVM, but isn't KVM-specific.
> >
> > However, this patch doesn't modify other in-kernel emulation code:
> > - xmon uses a direct copy of ppc_opc.c from binutils
> > - emulate_instruction() doesn't need it because it can use a series
> > of mask tests.
> >
> > Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
> > Acked-by: Paul Mackerras <paulus@samba.org>
Since tlbwe (et al) are now handled completely in core-specific code, I
don't see why you're asking...
--
Hollis Blanchard
IBM Linux Technology Center
prev parent reply other threads:[~2008-11-11 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 3:23 [PATCH 05 of 14] ppc: Create disassemble.h to extract instructionfields Liu Yu
2008-11-11 14:56 ` Hollis Blanchard [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=1226415380.458.2.camel@localhost.localdomain \
--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.