From: Janosch Frank <frankja@linux.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [PATCH 02/10] KVM: s390: add the GIB and its related life-cyle functions
Date: Wed, 31 Oct 2018 08:56:21 +0000 [thread overview]
Message-ID: <95e038f1-8d7b-bc9d-c553-bacbcc6d4410@linux.ibm.com> (raw)
In-Reply-To: <9461bcea-b3d2-2bd9-8408-8565d7de067e@de.ibm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: multipart/mixed; boundary="--XDjQN55Lte2ZufrDHe7XirFdE1xIorgNl", Size: 3593 bytes --]
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--XDjQN55Lte2ZufrDHe7XirFdE1xIorgNl
Content-Type: multipart/mixed; boundary="SjT5KeSPysEhjjRofzUUrumk4oX3hRDaq";
protected-headers="v1"
From: Janosch Frank <frankja@linux.ibm.com>
To: Michael Mueller <mimu@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
Sebastian Ott <sebott@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>, Julian Wiedmann <jwi@linux.vnet.ibm.com>,
Tony Krowiak <akrowiak@linux.vnet.ibm.com>,
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>, Thomas Huth <thuth@redhat.com>,
Pierre Morel <pmorel@linux.ibm.com>
Message-ID: <95e038f1-8d7b-bc9d-c553-bacbcc6d4410@linux.ibm.com>
Subject: Re: [PATCH 02/10] KVM: s390: add the GIB and its related life-cyle
functions
References: <20181025123751.48809-1-mimu@linux.ibm.com>
<20181025123751.48809-3-mimu@linux.ibm.com>
In-Reply-To: <20181025123751.48809-3-mimu@linux.ibm.com>
--SjT5KeSPysEhjjRofzUUrumk4oX3hRDaq
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
On 25.10.18 14:37, Michael Mueller wrote:
> The GIB (Guest Information Block) links the GISA of all guests
> that have adapter interrupts pending. These interrupts cannot be
> deliverd because no vcpu of these guests is currently running in
> SIE context. Instead, a GIB alert is issued on the host to schedule
> these guests to run.
>=20
> This mechanism allows to process adapter interrupts for currently
> not running guests.
>=20
> The GIB is created during host initialization and associated with
> the Adapter Interruption Facility in case an Adapter Interruption
> Virtualization Facility is available.
>=20
> Signed-off-by: Michael Mueller <mimu@linux.ibm.com>
> ---
> /*
> * sie_page2 has to be allocated as DMA because fac_list, crycb and
> * gisa need 31bit addresses in the sie control block.
> @@ -829,6 +838,7 @@ struct kvm_arch{
> /* subset of available cpu features enabled by user space */
> DECLARE_BITMAP(cpu_feat, KVM_S390_VM_CPU_FEAT_NR_BITS);
> struct kvm_s390_gisa *gisa;
> + int gib_in_use;
> };
That's a kvm wide value, right? But here we save it per VM.
Is that really necessary or am I missing something?
--SjT5KeSPysEhjjRofzUUrumk4oX3hRDaq--
--XDjQN55Lte2ZufrDHe7XirFdE1xIorgNl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJb2W41AAoJEONU5rjiOLn47IoP/A6WyM3+0TFkzBHrvbX7n/gI
NbaV3+ifH65fIk2vbo1jskoW/Er4AcnhC+3vcMJwkIpKUWfq/8EaoRWzdFUM3xvg
1Jydb0n9RZ9RPnH2mKxTmIZOm5SUrxScicTI0yc0bEO1ktySnJRxU44ZULEQSbrE
pLGVJScg+kfJrM653d0njL0LctanPoxvzE6C1ktWIK9LiL1nsxPkjoVH3YQQDoms
++s/V2QuY4ue2qCBuGBOc5WXt+fNqfvdn52zplTFm07kmVSasApSZ2nwa7Vfbnb5
yoyop1QO68Hd5QAvwYNFX2dL3Qk8uqcnxlx5tV8ejArxfGv3M/wuDQaul7muPQTN
RG7F7zCALDIRmYZK2/CXu85bIINnI9D4P1Lw8NnIxGUBSkw7dYHwoDPPZ7LRZmBb
BhicHtSmOnlJDyHCpMuUPj7Qh55j/UraoblZ5igP2OJMr2OyA04QYyKWNWq0aOIX
nNugzb7KzHDM0OWEyAtfNl5eQNGiE7iJu0xMBLgPKh+WwIHXTzezcLalxDUjX+K6
l1gmyf/E7B5nSlHo4F+O/wGOcS3dHZiO0ua72J7rF8u03tK2QgX4H2KRSdTrOVob
C1uAb0jGWiBQ7dGmafldoH8i8ncsQ+6D56caf0ocX/0DNXMpuLoZS8Rk9NHU3Huc
j80zWt3YOE1djDIvYzbN
=MBPT
-----END PGP SIGNATURE-----
--XDjQN55Lte2ZufrDHe7XirFdE1xIorgNl--
next parent reply other threads:[~2018-10-31 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9461bcea-b3d2-2bd9-8408-8565d7de067e@de.ibm.com>
2018-10-31 8:56 ` Janosch Frank [this message]
[not found] <142597db-3a87-9360-5463-f72275c1545f@linux.ibm.com>
2018-11-06 18:46 ` [PATCH 02/10] KVM: s390: add the GIB and its related life-cyle functions Pierre Morel
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=95e038f1-8d7b-bc9d-c553-bacbcc6d4410@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=linux-s390@vger.kernel.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