From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Janosch Frank <frankja@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
David Hildenbrand <david@redhat.com>,
Michael Mueller <mimu@linux.vnet.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] KVM: s390: do not set intervention requests for GISA interrupts
Date: Tue, 13 Feb 2018 16:48:19 +0100 [thread overview]
Message-ID: <20180213164819.392cf891.cohuck@redhat.com> (raw)
In-Reply-To: <20180213122858.74748-3-borntraeger@de.ibm.com>
On Tue, 13 Feb 2018 12:28:58 +0000
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> If GISA is available, we do not have to kick CPUs out of SIE to deliver
> interrupts. The hardware can deliver such interrupts while running.
>
> Cc: Michael Mueller <mimu@linux.vnet.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> arch/s390/kvm/interrupt.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2018-02-13 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:28 [PATCH 0/2] small optimizations for exitless interrupts Christian Borntraeger
2018-02-13 12:28 ` [PATCH 1/2] KVM: s390: optimize wakeup " Christian Borntraeger
2018-02-13 13:40 ` David Hildenbrand
2018-02-13 15:46 ` Cornelia Huck
2018-02-13 12:28 ` [PATCH 2/2] KVM: s390: do not set intervention requests for GISA interrupts Christian Borntraeger
2018-02-13 13:42 ` David Hildenbrand
2018-02-13 15:48 ` Cornelia Huck [this message]
2018-02-14 8:38 ` [PATCH 0/2] small optimizations for exitless interrupts Christian Borntraeger
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=20180213164819.392cf891.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mimu@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.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).