qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/7] s390x: next batch of patches
Date: Mon, 13 Jun 2016 10:19:26 +0200	[thread overview]
Message-ID: <575E6C8E.1030804@de.ibm.com> (raw)
In-Reply-To: <1465383765-18754-1-git-send-email-cornelia.huck@de.ibm.com>

On 06/08/2016 01:02 PM, Cornelia Huck wrote:
> More s390x patches, this time mostly dealing with channel I/O:
> Bugfixes and cleanups, and dequeue pending interrupts after
> machine checks.
> 
> Christian Borntraeger (3):
>   virtio-ccw: Provide traces for indicator changes
>   s390x: Limit s390-ccw machines to 248 CPUs
>   s390x/kvm: Fixup interrupt type for non-adapter I/O interrupts
> 
> Cornelia Huck (2):
>   linux-headers: update
>   s390x/css: introduce property type for device ids
> 
> Halil Pasic (2):
>   s390x/kvm: add interface for clearing IO irqs
>   s390x/css: clear IO irqs when generating IPI CRW
> 
>  hw/intc/s390_flic.c                            |   8 ++
>  hw/intc/s390_flic_kvm.c                        |  26 ++++++
>  hw/s390x/css.c                                 | 124 ++++++++++++++++++++++++-
>  hw/s390x/s390-virtio-ccw.c                     |   2 +-
>  hw/s390x/virtio-ccw.c                          |  80 +++++++---------
>  hw/s390x/virtio-ccw.h                          |   2 +-
>  include/hw/s390x/css.h                         |  17 ++++
>  include/hw/s390x/s390_flic.h                   |   2 +
>  include/standard-headers/linux/pci_regs.h      |  20 +++-
>  include/standard-headers/linux/virtio_config.h |   2 +
>  linux-headers/asm-arm/unistd.h                 |   2 +
>  linux-headers/asm-arm64/unistd.h               |   3 +
>  linux-headers/asm-powerpc/unistd.h             |   2 +
>  linux-headers/asm-s390/kvm.h                   |   1 +
>  linux-headers/asm-s390/unistd.h                |   4 +-
>  linux-headers/asm-x86/kvm.h                    |   6 +-
>  linux-headers/asm-x86/unistd_x32.h             |   2 +
>  linux-headers/linux/kvm.h                      |   1 +
>  target-s390x/kvm.c                             |   5 +-
>  trace-events                                   |   1 +
>  20 files changed, 251 insertions(+), 59 deletions(-)
> 

Selection looks good to me.

      parent reply	other threads:[~2016-06-13  8:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 11:02 [Qemu-devel] [PATCH 0/7] s390x: next batch of patches Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 1/7] linux-headers: update Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 2/7] s390x/kvm: add interface for clearing IO irqs Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 3/7] s390x/css: clear IO irqs when generating IPI CRW Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 4/7] s390x/css: introduce property type for device ids Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 5/7] virtio-ccw: Provide traces for indicator changes Cornelia Huck
2016-06-14 11:56   ` Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 6/7] s390x: Limit s390-ccw machines to 248 CPUs Cornelia Huck
2016-06-08 11:02 ` [Qemu-devel] [PATCH 7/7] s390x/kvm: Fixup interrupt type for non-adapter I/O interrupts Cornelia Huck
2016-06-13  8:19 ` Christian Borntraeger [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=575E6C8E.1030804@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --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).