From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
Alexander Graf <agraf@suse.de>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULL 09/11] KVM: s390: add bitmap for handling cpu-local interrupts
Date: Mon, 01 Dec 2014 15:59:38 +0100 [thread overview]
Message-ID: <1417445760-sup-7985@linux.vnet.ibm.com> (raw)
In-Reply-To: <547A3506.1080908@de.ibm.com>
Excerpts from Christian Borntraeger's message of 2014-11-29 22:05:10 +0100:
> Am 28.11.2014 um 18:18 schrieb Paolo Bonzini:
> >
> >
> > On 28/11/2014 14:25, Christian Borntraeger wrote:
> >>
> >> +struct kvm_s390_irq_payload {
> >> + struct kvm_s390_io_info io;
> >> + struct kvm_s390_ext_info ext;
> >> + struct kvm_s390_pgm_info pgm;
> >> + struct kvm_s390_emerg_info emerg;
> >> + struct kvm_s390_extcall_info extcall;
> >> + struct kvm_s390_prefix_info prefix;
> >> + struct kvm_s390_mchk_info mchk;
> >> +};
> >> +
> >
> > struct or union?
>
> struct. This is used for keeping the payload of the interrupts. Multiple different interrupts can be pending and most of them have payload - we want to keep everything.
>
> Now, looking at that code again, as I/O is floating and emergency is also handled via a separate bitmap we could get rid of these two in a follow-up patch. Jens, can you have a look and prepare a followup-cleanup if appropriate?
I/O is floating and currently not used in that struct, but I have a patch
series in the works to change floating interrupts as well and will need it then.
I will check if I can get rid of the emerg_info and sent a followup patch.
Jens
> Christian
next prev parent reply other threads:[~2014-12-01 14:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 13:25 [GIT PULL 00/11] KVM: s390: Several changes for 3.19 (kvm/next) Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 01/11] KVM: s390: Small fixes for the PFMF handler Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 02/11] KVM: s390: Fix rewinding of the PSW pointing to an EXECUTE instruction Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 03/11] KVM: s390: trigger the right CPU exit for floating interrupts Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 04/11] KVM: S390: Create helper function get_guest_storage_key Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 05/11] KVM: s390: refactor interrupt injection code Christian Borntraeger
2014-11-28 17:16 ` Paolo Bonzini
2014-12-01 8:00 ` Christian Borntraeger
2014-12-01 8:22 ` Jens Freimann
2014-11-28 13:25 ` [GIT PULL 06/11] KVM: s390: external param not valid for cpu timer and ckc Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 07/11] KVM: s390: add defines for virtio and pfault interrupt code Christian Borntraeger
2014-11-28 13:25 ` [GIT PULL 08/11] KVM: s390: refactor interrupt delivery code Christian Borntraeger
2014-11-28 17:17 ` Paolo Bonzini
2014-11-28 13:25 ` [GIT PULL 09/11] KVM: s390: add bitmap for handling cpu-local interrupts Christian Borntraeger
2014-11-28 17:18 ` Paolo Bonzini
2014-11-29 21:05 ` Christian Borntraeger
2014-12-01 14:59 ` Jens Freimann [this message]
2014-12-01 8:18 ` Jens Freimann
2014-11-28 13:25 ` [GIT PULL 10/11] KVM: s390: handle pending local interrupts via bitmap Christian Borntraeger
2014-12-01 8:19 ` Heiko Carstens
2014-12-01 9:46 ` Jens Freimann
2014-11-28 13:25 ` [GIT PULL 11/11] KVM: s390: allow injecting all kinds of machine checks Christian Borntraeger
2014-11-28 17:20 ` [GIT PULL 00/11] KVM: s390: Several changes for 3.19 (kvm/next) Paolo Bonzini
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=1417445760-sup-7985@linux.vnet.ibm.com \
--to=jfrei@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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).