linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc <kvm-ppc@vger.kernel.org>,
	kvm@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PPC: Sync guest visible MMU state
Date: Tue, 24 Nov 2009 17:02:42 +0200	[thread overview]
Message-ID: <4B0BF592.9020802@redhat.com> (raw)
In-Reply-To: <1259049003-8028-1-git-send-email-agraf@suse.de>

On 11/24/2009 09:50 AM, Alexander Graf wrote:
> Currently userspace has no chance to find out which virtual address space we're
> in and resolve addresses. While that is a big problem for migration, it's also
> unpleasent when debugging, as gdb and the monitor don't work on virtual
> addresses.
>    

> index 92045a9..1240fcb 100644
> --- a/include/linux/kvm.h
> +++ b/include/linux/kvm.h
> @@ -492,6 +492,7 @@ struct kvm_ioeventfd {
>   #ifdef __KVM_HAVE_VCPU_EVENTS
>   #define KVM_CAP_VCPU_EVENTS 41
>   #endif
> +#define KVM_CAP_PPC_SEGSTATE 42
>
>    

42 is already taken (s390 psw and D. Adams), please use 43.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-11-24 15:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  7:50 [PATCH] PPC: Sync guest visible MMU state Alexander Graf
2009-11-24 15:02 ` Avi Kivity [this message]
2009-11-24 15:04   ` Alexander Graf
2009-11-24 16:05     ` Avi Kivity
2009-11-26 11:16 Alexander Graf
2009-11-26 12:40 ` Avi Kivity
2009-11-26 12:46   ` Alexander Graf
2009-11-26 12:50     ` Avi Kivity
2009-11-26 13:16       ` Alexander Graf
2009-11-26 13:20         ` Avi Kivity
2009-11-26 15:24 Alexander Graf
2009-11-26 21:56 ` Alexander Graf
2009-11-30 13:02 Alexander Graf
2009-11-30 13:15 ` Avi Kivity

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=4B0BF592.9020802@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).