From: David Hildenbrand <david@redhat.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH RFC 2/5] s390x: implement diag260
Date: Fri, 10 Jul 2020 17:45:42 +0200 [thread overview]
Message-ID: <50DB9C15-AE46-4F41-83F3-A18D1E86B6FA@redhat.com> (raw)
In-Reply-To: <20200710154302.GD14845@osiris>
> Am 10.07.2020 um 17:43 schrieb Heiko Carstens <hca@linux.ibm.com>:
>
> On Fri, Jul 10, 2020 at 05:24:07PM +0200, David Hildenbrand wrote:
>>> On 10.07.20 17:18, Heiko Carstens wrote:
>>> On Fri, Jul 10, 2020 at 02:12:33PM +0200, David Hildenbrand wrote:
>>>>> Note: Reading about diag260 subcode 0xc, we could modify Linux to query
>>>>> the maximum possible pfn via diag260 0xc. Then, we maybe could avoid
>>>>> indicating maxram size via SCLP, and keep diag260-unaware OSs keep
>>>>> working as before. Thoughts?
>>>>
>>>> Implemented it, seems to work fine.
>>>
>>> The returned value would not include standby/reserved memory within
>>> z/VM. So this seems not to work.
>>
>> Which value exactly are you referencing? diag 0xc returns two values.
>> One of them seems to do exactly what we need.
>
> Maybe I'm missing something as usual, but to me this
> --------
> Usage Notes:
> ...
> 2. If the RESERVED or STANDBY option was used on the DEFINE STORAGE
> command to configure reserved or standby storage for a guest, the
> values returned in Rx and Ry will be the current values, but these
> values can change dynamically depending on the options specified and
> any dynamic storage reconfiguration (DSR) changes initiated by the
> guest.
> --------
> reads like it is not doing what you want. That is: it does *not*
> include standby memory and therefore will not return the highest
> possible pfn.
>
Ah, yes. See the kernel patch, I take the max of both values (SCLP, diag260(0xc)) values.
Anyhow, what would be your recommendation?
Thanks!
next prev parent reply other threads:[~2020-07-10 15:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 18:51 [PATCH RFC 0/5] s390x: initial support for virtio-mem David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 1/5] s390x: move setting of maximum ram size to machine init David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 2/5] s390x: implement diag260 David Hildenbrand
2020-07-09 10:37 ` Cornelia Huck
2020-07-09 17:54 ` David Hildenbrand
2020-07-10 8:32 ` David Hildenbrand
2020-07-10 8:41 ` David Hildenbrand
2020-07-10 9:19 ` Cornelia Huck
2020-07-13 11:54 ` Christian Borntraeger
2020-07-13 12:11 ` Cornelia Huck
2020-07-13 12:13 ` Christian Borntraeger
2020-07-09 10:52 ` Christian Borntraeger
2020-07-09 18:15 ` David Hildenbrand
2020-07-10 9:17 ` David Hildenbrand
2020-07-10 12:12 ` David Hildenbrand
2020-07-10 15:18 ` Heiko Carstens
2020-07-10 15:24 ` David Hildenbrand
2020-07-10 15:43 ` Heiko Carstens
2020-07-10 15:45 ` David Hildenbrand [this message]
2020-07-13 9:12 ` Heiko Carstens
2020-07-13 10:27 ` David Hildenbrand
2020-07-13 11:08 ` Christian Borntraeger
2020-07-15 9:42 ` David Hildenbrand
2020-07-15 10:43 ` Heiko Carstens
2020-07-15 11:21 ` David Hildenbrand
2020-07-15 11:34 ` Heiko Carstens
2020-07-15 11:42 ` David Hildenbrand
2020-07-15 16:14 ` Heiko Carstens
2020-07-15 17:38 ` David Hildenbrand
2020-07-15 17:51 ` David Hildenbrand
2020-07-20 14:43 ` Heiko Carstens
2020-07-20 15:43 ` David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 3/5] s390x: prepare device memory address space David Hildenbrand
2020-07-09 10:59 ` Cornelia Huck
2020-07-10 7:46 ` David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 4/5] s390x: implement virtio-mem-ccw David Hildenbrand
2020-07-09 9:24 ` Cornelia Huck
2020-07-09 9:26 ` David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 5/5] s390x: initial support for virtio-mem David Hildenbrand
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=50DB9C15-AE46-4F41-83F3-A18D1E86B6FA@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@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).