From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com, david@redhat.com,
borntraeger@de.ibm.com, frankja@linux.ibm.com
Subject: [kvm-unit-tests PATCH v1 3/5] s390x: sclp: expose ram_size and max_ram_size
Date: Tue, 22 Oct 2019 12:53:02 +0200 [thread overview]
Message-ID: <1571741584-17621-4-git-send-email-imbrenda@linux.ibm.com> (raw)
In-Reply-To: <1571741584-17621-1-git-send-email-imbrenda@linux.ibm.com>
Expose ram_size and max_ram_size through accessor functions.
We only use get_ram_size in an upcoming patch, but having an accessor
for the other one does not hurt.
Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
lib/s390x/sclp.h | 2 ++
lib/s390x/sclp.c | 9 +++++++++
2 files changed, 11 insertions(+)
diff --git a/lib/s390x/sclp.h b/lib/s390x/sclp.h
index f00c3df..6d40fb7 100644
--- a/lib/s390x/sclp.h
+++ b/lib/s390x/sclp.h
@@ -272,5 +272,7 @@ void sclp_console_setup(void);
void sclp_print(const char *str);
int sclp_service_call(unsigned int command, void *sccb);
void sclp_memory_setup(void);
+uint64_t get_ram_size(void);
+uint64_t get_max_ram_size(void);
#endif /* SCLP_H */
diff --git a/lib/s390x/sclp.c b/lib/s390x/sclp.c
index 56fca0c..a57096c 100644
--- a/lib/s390x/sclp.c
+++ b/lib/s390x/sclp.c
@@ -167,3 +167,12 @@ void sclp_memory_setup(void)
mem_init(ram_size);
}
+
+uint64_t get_ram_size(void)
+{
+ return ram_size;
+}
+uint64_t get_max_ram_size(void)
+{
+ return max_ram_size;
+}
--
2.7.4
next prev parent reply other threads:[~2019-10-22 10:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 10:52 [kvm-unit-tests PATCH v1 0/5] s390x: SCLP Unit test Claudio Imbrenda
2019-10-22 10:53 ` [kvm-unit-tests PATCH v1 1/5] s390x: remove redundant defines Claudio Imbrenda
2019-10-22 11:54 ` Thomas Huth
2019-10-22 15:44 ` David Hildenbrand
2019-10-22 10:53 ` [kvm-unit-tests PATCH v1 2/5] s390x: improve error reporting for interrupts Claudio Imbrenda
2019-10-22 11:56 ` Thomas Huth
2019-10-22 15:44 ` David Hildenbrand
2019-10-22 10:53 ` Claudio Imbrenda [this message]
2019-10-22 12:16 ` [kvm-unit-tests PATCH v1 3/5] s390x: sclp: expose ram_size and max_ram_size Thomas Huth
2019-10-22 15:44 ` David Hildenbrand
2019-10-22 10:53 ` [kvm-unit-tests PATCH v1 4/5] s390x: sclp: add service call instruction wrapper Claudio Imbrenda
2019-10-22 12:11 ` Thomas Huth
2019-10-22 15:46 ` David Hildenbrand
2019-10-22 10:53 ` [kvm-unit-tests PATCH v1 5/5] s390x: SCLP unit test Claudio Imbrenda
2019-10-23 12:14 ` David Hildenbrand
2019-10-25 13:37 ` Claudio Imbrenda
2019-10-23 12:48 ` Thomas Huth
2019-10-24 15:40 ` Claudio Imbrenda
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=1571741584-17621-4-git-send-email-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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