All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Martin <dave.martin@linaro.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Will Deacon <will.deacon@arm.com>,
	Christoffer Dall <c.dall@virtualopensystems.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: RFC: Move kvm's instruction decoding into generic code.
Date: Wed, 24 Oct 2012 17:27:58 +0100	[thread overview]
Message-ID: <20121024162758.GB2005@linaro.org> (raw)
In-Reply-To: <1351077923-17977-1-git-send-email-rusty@rustcorp.com.au>

On Wed, Oct 24, 2012 at 09:55:13PM +1030, Rusty Russell wrote:
> Compile-tested only, but shows what it looks like (ugly).
> 
> I just used the existing code and didn't crack open my ARM books to
> determine if there's a better way.  The struct names are pretty vague,
> too, as a result.
> 

Thanks (to you and Christoffer) for having a stab at this.

I'll try to respond to these patches, but I have a recorsive panic
going on here so it may take a bit of time...

Cheers
---Dave

      parent reply	other threads:[~2012-10-24 16:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  7:58 [PATCH 0/3] KVM_VCPU_GET_REG_LIST API Rusty Russell
2012-09-05  7:58 ` [PATCH 1/3] KVM: Move KVM_SET_ONE_REG/KVM_GET_ONE_REG to generic code Rusty Russell
2012-09-19 14:17   ` Alexander Graf
2012-09-05  7:58 ` [PATCH 2/3] KVM: Add KVM_REG_SIZE() helper Rusty Russell
2012-09-19 14:18   ` Alexander Graf
2012-09-05  7:58 ` [PATCH 3/3] KVM: Add KVM_VCPU_GET_REG_LIST/KVM_CAP_REG_LIST Rusty Russell
2012-09-19 14:22   ` Alexander Graf
2012-10-10 18:12   ` Marcelo Tosatti
2012-10-11  8:11     ` Rusty Russell
2012-10-18 14:45 ` [PATCH 0/3] KVM_VCPU_GET_REG_LIST API Avi Kivity
2012-10-19  0:36   ` Rusty Russell
2012-10-19  6:19     ` Rusty Russell
2012-10-19 16:06       ` Christoffer Dall
2012-10-22  3:09         ` Rusty Russell
2012-10-22 17:45           ` Will Deacon
2012-10-22 18:11             ` Christoffer Dall
2012-10-24 11:25             ` RFC: Move kvm's instruction decoding into generic code Rusty Russell
2012-10-24 11:25               ` [PATCH 01/10] kvm: split out instruction structure from decoding method Rusty Russell
2012-10-24 11:25               ` [PATCH 02/10] kvm: split out instruction decode from emulation Rusty Russell
2012-10-24 11:25               ` [PATCH 03/10] kvm: split out instruction decode from emulation (thumb instructions) Rusty Russell
2012-10-24 11:25               ` [PATCH 04/10] kvm: completely separate decoding from execution Rusty Russell
2012-10-24 11:25               ` [PATCH 05/10] kvm: move instruction copying inside kvm_decode() Rusty Russell
2012-10-24 11:25               ` [PATCH 06/10] kvm: cleanup use of instr Rusty Russell
2012-10-24 11:25               ` [PATCH 07/10] kvm: clean up use of is_wide_instruction() Rusty Russell
2012-10-24 11:25               ` [PATCH 08/10] kvm: avoid using vcpu_cpsr() by passing down PSR Rusty Russell
2012-10-24 11:25               ` [PATCH 09/10] kvm: avoid reference vcpu->arch.hxfar by making thumb offset_addr relative Rusty Russell
2012-10-24 11:25               ` [PATCH 10/10] opcode: move generic instruction decode out of KVM Rusty Russell
2012-10-24 16:27               ` Dave Martin [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=20121024162758.GB2005@linaro.org \
    --to=dave.martin@linaro.org \
    --cc=c.dall@virtualopensystems.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=will.deacon@arm.com \
    /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.