All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Rusty Russell <rusty.russell@linaro.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Christoffer Dall <c.dall@virtualopensystems.com>,
	kvmarm@lists.cs.columbia.edu, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-arm: kvm: use KVM_SET_SREGS to set target to Cortex A15
Date: Wed, 25 Jul 2012 16:04:40 +0100	[thread overview]
Message-ID: <CAFEAcA86Rv1vcqtem=Z3bPa1R+1w3fZS0tDnF16DKc0jFHLAmg@mail.gmail.com> (raw)
In-Reply-To: <87394gpdoi.fsf@rustcorp.com.au>

On 25 July 2012 07:17, Rusty Russell <rusty.russell@linaro.org> wrote:
> On Tue, 17 Jul 2012 19:19:16 +0100, Peter Maydell <peter.maydell@linaro.org> wrote:
>> So I can't see anything better than "complain and return failure
>> from kvm_arch_init_vcpu() if the guest CPU isn't going to work".
>
> OK, here's what I have for kvm.  It matches the kernel patches I just
> sent out, with the updated API.
>
> I rewrote all the backwards compat stuff to wrap it in #ifdef
> HORRIBLE_COMPAT_HACK, but something subtle broke and it no longer set
> cpsr correctly for older kernels.  After wasting an afternoon on it, I
> gave up and threw out the backwards compat code in digust.
>
> Nor does it bisect, since we update the headers as you asked, then
> update the code.

Looks ok. We'll probably rewrite that register read/write code
at some point before upstreaming -- I want to see if we
can do that as a straightforward "iterate through cp15 hash
table and do something for every register" kind of loop,
but this is OK for purposes of staying in sync with the kernel.

I'm going to hold off on putting this in qemu-linaro until Christoffer
has acked the ABI changes on the kernel side, though.

>       Local update of linux-headers/asm-arm/kvm.h

>From the commit message for that:
# Worse, the new arm kvm_para.h includes asm-generic/kvm_para.h,
# which isn't included in qemu.

That we can deal with now, though: update-linux-headers.sh
just needs updating to include it in its non-arch-specific
set of copied headers.

-- PMM

  reply	other threads:[~2012-07-25 15:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13  3:37 [Qemu-devel] [PATCH] target-arm: kvm: use KVM_SET_SREGS to set target to Cortex A15 Rusty Russell
2012-07-13  3:43 ` [Qemu-devel] [PATCH 2/3] target-arm: kvm: use KVM_GET_MSRS/KVM_SET_MSRS for CP15 registers Rusty Russell
2012-07-13 14:27   ` Blue Swirl
2012-07-13  3:43 ` [Qemu-devel] [PATCH 3/3] target-arm: kvm: remove old kernel support Rusty Russell
2012-07-13  8:06 ` [Qemu-devel] [PATCH] target-arm: kvm: use KVM_SET_SREGS to set target to Cortex A15 Peter Maydell
2012-07-16  7:22   ` Rusty Russell
2012-07-13 10:06 ` [Qemu-devel] [kvmarm] " Alexander Graf
2012-07-16  7:19   ` Rusty Russell
2012-07-16  8:08     ` Alexander Graf
2012-07-16  8:09     ` Avi Kivity
2012-07-17 17:31 ` [Qemu-devel] " Peter Maydell
2012-07-17 18:19   ` Peter Maydell
2012-07-25  6:17     ` Rusty Russell
2012-07-25 15:04       ` Peter Maydell [this message]
2012-07-31 21:52       ` [Qemu-devel] [kvmarm] " Antonios Motakis
2012-08-01  1:53         ` Rusty Russell

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='CAFEAcA86Rv1vcqtem=Z3bPa1R+1w3fZS0tDnF16DKc0jFHLAmg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=aliguori@us.ibm.com \
    --cc=c.dall@virtualopensystems.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty.russell@linaro.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.