public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Carsten Otte <carsteno@de.ibm.com>
Cc: Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	uli@suse.de, Carsten Otte <cotte@de.ibm.com>,
	hare@suse.de, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/9] S390x KVM support
Date: Thu, 22 Oct 2009 11:08:29 +0200	[thread overview]
Message-ID: <4AE0210D.9020409@redhat.com> (raw)
In-Reply-To: <4ADDE7E3.9090601@de.ibm.com>

On 10/20/2009 06:40 PM, Carsten Otte wrote:
>
> This patch moves s390 processor status word into the base kvm_run
> struct and keeps it up-to date on all userspace exits.
>
> +#include <linux/autoconf.h>
> #include <linux/types.h>
> #include <linux/compiler.h>
> #include <linux/ioctl.h>

Not needed.

> @@ -116,6 +117,11 @@
>     __u64 cr8;
>     __u64 apic_base;
>
> +#ifdef CONFIG_S390
> +    /* the processor status word for s390 */
> +    __u64 psw_mask; /* psw upper half */
> +    __u64 psw_addr; /* psw lower half */
> +#endif

Doesn't this break backward compatibility by changing the structure?

Best to put it after the union (and as a copy, so userspace that expects 
the previous location still works).  If you're reading it from the 
kernel, also need a way to tell the kernel which copy to read from.

Also advertise with a KVM_CAP.

Additionally, CONFIG_ in public headers are frowned upon as 
non-portable.  A workaround is to #define __KVM_S390 in <asm/kvm.h> and 
depend on that.

> --- kvm.orig/arch/s390/kvm/kvm-s390.c    2009-10-20 15:01:02.000000000 
> +0200
> +++ kvm/arch/s390/kvm/kvm-s390.c    2009-10-20 18:13:45.000000000 +0200
> @@ -421,7 +421,8 @@
>     if (atomic_read(&vcpu->arch.sie_block->cpuflags) & CPUSTAT_RUNNING)
>         rc = -EBUSY;
>     else
> -        vcpu->arch.sie_block->gpsw = psw;
> +        vcpu->run->psw_mask = psw.mask;
> +        vcpu->run->psw_addr = psw.addr;

It's traditional to add braces around multi-line else blocks.

I'd also appreciate an explanation of what this is all about.

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


       reply	other threads:[~2009-10-22  9:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1255963059-10298-1-git-send-email-agraf@suse.de>
     [not found] ` <4ADDE7E3.9090601@de.ibm.com>
2009-10-22  9:08   ` Avi Kivity [this message]
2009-10-22  9:11     ` [PATCH 0/9] S390x KVM support Alexander Graf
2009-10-22  9:53       ` Avi Kivity
2009-10-22  9:55         ` Alexander Graf
2009-10-22  9:58           ` Alexander Graf
2009-10-22 10:03           ` Avi Kivity
2009-10-22 10:13             ` Alexander Graf
2009-10-22 10:22             ` Carsten Otte
2009-10-22 10:28               ` Avi Kivity
2009-10-22 10:43                 ` Carsten Otte
2009-10-22 10:49                   ` Avi Kivity
2009-10-22 11:10                     ` Carsten Otte
2009-11-02 20:23                       ` Alexander Graf
2009-11-03  8:55                         ` Avi Kivity
2009-10-22  9:18     ` Carsten Otte
2009-10-22 10:02       ` Avi Kivity
2009-10-22 10:20         ` Carsten Otte
2009-10-22 10:29           ` 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=4AE0210D.9020409@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=carsteno@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=hare@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=uli@suse.de \
    /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