From: Janosch Frank <frankja@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v5 1/7] s390/uv: Always export uv_info
Date: Fri, 16 Jun 2023 10:56:17 +0200 [thread overview]
Message-ID: <08ed39eb-b1cf-7c15-83a4-dd59cc29732b@linux.ibm.com> (raw)
In-Reply-To: <20230615100533.3996107-2-seiden@linux.ibm.com>
On 6/15/23 12:05, Steffen Eiden wrote:
> KVM needs the struct's values to be able to provide PV support.
>
> The uvdevice is currently guest only and will need the struct's values
> for call support checking and potential future expansions.
>
> As uv.c is only compiled with CONFIG_PGSTE or
> CONFIG_PROTECTED_VIRTUALIZATION_GUEST we don't need a second check in
> the code. Users of uv_info will need to fence for these two config
> options for the time being.
>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
In the long term we'll remove the config checks and always compile uv.o
in kernel/ and boot/ so we won't be running in these issues again.
next prev parent reply other threads:[~2023-06-16 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 10:05 [PATCH v5 0/7] s390/uvdevice: Expose secret UVCs Steffen Eiden
2023-06-15 10:05 ` [PATCH v5 1/7] s390/uv: Always export uv_info Steffen Eiden
2023-06-16 8:56 ` Janosch Frank [this message]
2023-06-15 10:05 ` [PATCH v5 2/7] s390/uvdevice: Add info IOCTL Steffen Eiden
2023-06-15 10:05 ` [PATCH v5 3/7] s390/uvdevice: Add 'Add Secret' UVC Steffen Eiden
2023-06-15 10:05 ` [PATCH v5 4/7] s390/uvdevice: Add 'List Secrets' UVC Steffen Eiden
2023-06-15 10:05 ` [PATCH v5 5/7] s390/uvdevice: Add 'Lock Secret Store' UVC Steffen Eiden
2023-06-15 10:05 ` [PATCH v5 6/7] s390/uv: replace scnprintf with sysfs_emit Steffen Eiden
2023-06-15 10:05 ` [PATCH v5 7/7] s390/uv: Update query for secret-UVCs Steffen Eiden
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=08ed39eb-b1cf-7c15-83a4-dd59cc29732b@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=seiden@linux.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