From: Alexander Graf <agraf@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>, KVM list <kvm@vger.kernel.org>,
	Carsten Otte <carsteno@de.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	hare@suse.de
Subject: [Qemu-devel] Re: [PATCH 0/9] S390x KVM support
Date: Thu, 22 Oct 2009 11:11:20 +0200	[thread overview]
Message-ID: <98DC9E4C-7FFA-4F05-A2E8-0B5DF546891C@suse.de> (raw)
In-Reply-To: <4AE0210D.9020409@redhat.com>
On 22.10.2009, at 11:08, Avi Kivity wrote:
> 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.
I don't think we need to go through the hassle here. There is  
effectively no user of that code for now and the ABI is considered  
unstable.
> 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.
Explanation in the code or explanation in an email reply?
Alex
next prev parent reply	other threads:[~2009-10-22  9:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 14:37 [Qemu-devel] [PATCH 0/9] S390x KVM support Alexander Graf
2009-10-19 14:37 ` [Qemu-devel] [PATCH 1/9] Export function for VA defined ram allocation Alexander Graf
2009-10-19 14:37   ` [Qemu-devel] [PATCH 2/9] Add KVM support for S390x Alexander Graf
2009-10-19 14:37     ` [Qemu-devel] [PATCH 3/9] Add support for S390x system emulation Alexander Graf
2009-10-19 14:37       ` [Qemu-devel] [PATCH 4/9] Add S390x virtio machine bus Alexander Graf
2009-10-19 14:37         ` [Qemu-devel] [PATCH 5/9] Add S390x virtio machine description Alexander Graf
2009-10-19 14:37           ` [Qemu-devel] [PATCH 6/9] S390 GDB stub Alexander Graf
2009-10-19 14:37             ` [Qemu-devel] [PATCH 7/9] Implement early printk in virtio-console Alexander Graf
2009-10-19 14:37               ` [Qemu-devel] [PATCH 8/9] Set default console to virtio on S390x Alexander Graf
2009-10-19 14:37                 ` [Qemu-devel] [PATCH 9/9] Move mp_state to CPU_COMMON Alexander Graf
2009-10-19 19:48                 ` [Qemu-devel] [PATCH 8/9] Set default console to virtio on S390x Gerd Hoffmann
2009-10-19 19:34         ` [Qemu-devel] [PATCH 4/9] Add S390x virtio machine bus Gerd Hoffmann
2009-10-19 19:40           ` Alexander Graf
2009-10-19 20:10             ` Gerd Hoffmann
2009-10-20  8:36     ` [Qemu-devel] Re: [PATCH 2/9] Add KVM support for S390x Carsten Otte
2009-10-20  8:41       ` Alexander Graf
2009-10-20  8:02   ` [Qemu-devel] Re: [PATCH 1/9] Export function for VA defined ram allocation Carsten Otte
2009-10-19 19:24 ` [Qemu-devel] [PATCH 0/9] S390x KVM support Gerd Hoffmann
2009-10-19 19:32   ` Alexander Graf
2009-10-20  5:05 ` Avi Kivity
2009-10-20 16:40 ` [Qemu-devel] " Carsten Otte
2009-10-21  7:20   ` Alexander Graf
2009-10-21  7:24   ` Alexander Graf
2009-10-21  8:18     ` Carsten Otte
2009-10-21  8:23       ` Alexander Graf
2009-10-21  7:26   ` Alexander Graf
2009-10-22  9:08   ` Avi Kivity
2009-10-22  9:11     ` Alexander Graf [this message]
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=98DC9E4C-7FFA-4F05-A2E8-0B5DF546891C@suse.de \
    --to=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=carsteno@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=hare@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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).