From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
david@redhat.com, thuth@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH 4/5] s390x: smp: Allocate memory in DMA31 space
Date: Fri, 14 Jan 2022 14:01:23 +0100 [thread overview]
Message-ID: <20220114140123.10bf0406@p-imbrenda> (raw)
In-Reply-To: <f840f66aa615ce167187754842268662cd466b92.camel@linux.ibm.com>
On Fri, 14 Jan 2022 13:50:52 +0100
Nico Boehr <nrb@linux.ibm.com> wrote:
> On Fri, 2022-01-14 at 10:02 +0000, Janosch Frank wrote:
> > The store status at address order works with 31 bit addresses so
> > let's
> > use them.
> >
> > Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> > ---
> > s390x/smp.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/s390x/smp.c b/s390x/smp.c
> > index 32f128b3..c91f170b 100644
> > --- a/s390x/smp.c
> > +++ b/s390x/smp.c
>
> [...]
>
> > @@ -244,7 +244,7 @@ static void test_func_initial(void)
> >
> > static void test_reset_initial(void)
> > {
> > - struct cpu_status *status = alloc_pages(0);
> > + struct cpu_status *status = alloc_pages_flags(1, AREA_DMA31);
>
> Why do we need two pages now?
actually, wait.....
struct cpu_status *status = alloc_pages_flags(1, AREA_DMA31);
uint32_t r;
report_prefix_push("store status at address");
memset(status, 0, PAGE_SIZE * 2);
we were allocating one page, and using 2!
@Janosch do we need 1 or 2 pages?
next prev parent reply other threads:[~2022-01-14 13:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 10:02 [kvm-unit-tests PATCH 0/5] s390x: Allocation and hosting environment detection fixes Janosch Frank
2022-01-14 10:02 ` [kvm-unit-tests PATCH 1/5] lib: s390x: vm: Add kvm and lpar vm queries Janosch Frank
2022-01-14 11:18 ` Claudio Imbrenda
2022-01-14 12:28 ` Janosch Frank
2022-01-14 12:55 ` Claudio Imbrenda
2022-01-14 13:27 ` Nico Boehr
2022-01-14 13:35 ` Janosch Frank
2022-01-14 13:43 ` Nico Boehr
2022-01-14 10:02 ` [kvm-unit-tests PATCH 2/5] s390x: css: Skip if we're not run by qemu Janosch Frank
2022-01-14 10:41 ` Claudio Imbrenda
2022-01-17 7:01 ` Thomas Huth
2022-01-14 10:02 ` [kvm-unit-tests PATCH 3/5] s390x: diag308: Only test subcode 2 under QEMU Janosch Frank
2022-01-14 10:39 ` Claudio Imbrenda
2022-01-17 7:04 ` Thomas Huth
2022-01-17 9:39 ` Janosch Frank
2022-01-14 10:02 ` [kvm-unit-tests PATCH 4/5] s390x: smp: Allocate memory in DMA31 space Janosch Frank
2022-01-14 11:18 ` Claudio Imbrenda
2022-01-14 12:50 ` Nico Boehr
2022-01-14 12:57 ` Claudio Imbrenda
2022-01-14 13:07 ` Janosch Frank
2022-01-14 13:01 ` Claudio Imbrenda [this message]
2022-01-14 13:13 ` Janosch Frank
2022-01-14 13:16 ` Claudio Imbrenda
2022-01-14 13:18 ` Janosch Frank
2022-01-14 13:19 ` Claudio Imbrenda
2022-01-14 10:02 ` [kvm-unit-tests PATCH 5/5] s390x: firq: Fix sclp buffer allocation Janosch Frank
2022-01-14 11:19 ` Claudio Imbrenda
2022-01-14 11:19 ` [kvm-unit-tests PATCH 0/5] s390x: Allocation and hosting environment detection fixes Claudio Imbrenda
2022-01-14 12:23 ` Janosch Frank
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=20220114140123.10bf0406@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--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).