From: Reinoud Zandijk <reinoud@NetBSD.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Reinoud Zandijk <reinoud@netbsd.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1 2/2] Fix nvmm_ram_block_added() function arguments
Date: Mon, 19 Jul 2021 16:54:05 +0200 [thread overview]
Message-ID: <YPWSDefSns4ueQz3@gorilla.13thmonkey.org> (raw)
In-Reply-To: <CAFEAcA9qiT46qvAgD2cGSqo=FsJhJjCSxR+KBN+7XpvVaSgfuQ@mail.gmail.com>
Hi,
On Sun, Jul 18, 2021 at 05:38:58PM +0100, Peter Maydell wrote:
> On Sun, 18 Jul 2021 at 14:54, Reinoud Zandijk <reinoud@netbsd.org> wrote:
> > A parameter max_size was added to the RAMBlockNotifier
> > ram_block_added function. Use the max_size for pre allocation
> > of hva space.
> >
> > Signed-off-by: Reinoud Zandijk <Reinoud@NetBSD.org>
> > ---
> > target/i386/nvmm/nvmm-all.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/target/i386/nvmm/nvmm-all.c b/target/i386/nvmm/nvmm-all.c
> > index dfa690d65d..fdcd37ed3e 100644
> > --- a/target/i386/nvmm/nvmm-all.c
> > +++ b/target/i386/nvmm/nvmm-all.c
> > @@ -1134,13 +1134,14 @@ static MemoryListener nvmm_memory_listener = {
> > };
> >
> > static void
> > -nvmm_ram_block_added(RAMBlockNotifier *n, void *host, size_t size)
> > +nvmm_ram_block_added(RAMBlockNotifier *n, void *host, size_t size,
> > + size_t max_size)
> > {
> > struct nvmm_machine *mach = get_nvmm_mach();
> > uintptr_t hva = (uintptr_t)host;
> > int ret;
> >
> > - ret = nvmm_hva_map(mach, hva, size);
> > + ret = nvmm_hva_map(mach, hva, max_size);
> >
> > if (ret == -1) {
> > error_report("NVMM: Failed to map HVA, HostVA:%p "
>
> This suggests that this code isn't being covered by our CI. Is
> there something we can do to get it tested?
NVMM acceleration is currently NetBSD host only so can only be tested on
NetBSD hosts. Unless Qemu is smart enough to allow a guest NetBSD to run
NetBSD to test NVMM in a nested Qemu I don't think its possible to otherwise
automatically test on Linux.
Is there a README or documentation on how to modify and run the tests?
With regard,
Reinoud
next prev parent reply other threads:[~2021-07-19 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 13:46 [PATCH v1 0/2] Update NVMM support to recent changes Reinoud Zandijk
2021-07-18 13:46 ` [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined Reinoud Zandijk
2021-09-07 16:20 ` Philippe Mathieu-Daudé
2021-09-08 9:46 ` Reinoud Zandijk
2021-09-08 10:30 ` Philippe Mathieu-Daudé
2021-07-18 13:46 ` [PATCH v1 2/2] Fix nvmm_ram_block_added() function arguments Reinoud Zandijk
2021-07-18 16:38 ` Peter Maydell
2021-07-19 14:54 ` Reinoud Zandijk [this message]
2021-08-29 16:04 ` applied? Re: [PATCH v1 0/2] Update NVMM support to recent changes, [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined, " Reinoud Zandijk
2021-08-29 16:39 ` Peter Maydell
2021-09-07 16:02 ` Reinoud Zandijk
2021-09-10 16:21 ` Paolo Bonzini
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=YPWSDefSns4ueQz3@gorilla.13thmonkey.org \
--to=reinoud@netbsd.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).