qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Reinoud Zandijk <reinoud@NetBSD.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, Kamil Rytarowski <kamil@NetBSD.org>,
	Reinoud Zandijk <reinoud@NetBSD.org>,
	Ryo ONODERA <ryoon@netbsd.org>
Subject: Re: [PATCH v6 2/4] Add NVMM accelerator: x86 CPU support
Date: Thu, 1 Apr 2021 14:32:37 +0200	[thread overview]
Message-ID: <YGW9ZSo5RbeqDuVX@diablo.13thmonkey.org> (raw)
In-Reply-To: <5afd10b1-bd32-2f06-b311-246815428bfc@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]

On Thu, Apr 01, 2021 at 10:35:40AM +0200, Paolo Bonzini wrote:
> On 31/03/21 22:07, Reinoud Zandijk wrote:
> > +void nvmm_vcpu_kick(CPUState *cpu);
> 
> Not defined anywhere.

Hmmm, indeed. I think its a leftover of the former patch. Good catch.

> > +{
> > +#if NVMM_USER_VERSION == 1
> > +    struct sigaction sigact;
> > +    sigset_t set;
> > +
> > +    /* Install the IPI handler. */
> > +    memset(&sigact, 0, sizeof(sigact));
> > +    sigact.sa_handler = nvmm_ipi_signal;
> > +    sigaction(SIG_IPI, &sigact, NULL);
> > +
> > +    /* Allow IPIs on the current thread. */
> > +    sigprocmask(SIG_BLOCK, NULL, &set);
> > +    sigdelset(&set, SIG_IPI);
> > +    pthread_sigmask(SIG_SETMASK, &set, NULL);
> > +#else
> > +    /*
> > +     * We use the nvmm_vcpu_stop() mechanism, and don't use signals.
> > +     * Nothing to do.
> > +     */
> > +#endif
> 
> Since nvmm_vcpu_stop is very similar to KVM's immediate_exit mechanism, I
> think you still need to have a dummy signal handler to kick the VM out of
> the run loop *if it is in the kernel*.  The signal handler however can just
> do nothing.

Are you worried the in-kernel thread will somehow get stuck or halt on exit of
Qemu and left as a zombie?

> Also, can you just drop support for NVMM_USER_VERSION == 1?

Now thats a good suggestion. We could add support for it in the pkgsrc
package. When 9.0 gets retired, we could then retire it there without the need
to patch Qemu again.

> > diff --git a/target/i386/nvmm/meson.build b/target/i386/nvmm/meson.build
> > new file mode 100644
> > index 0000000000..c154e78014
> > --- /dev/null
> > +++ b/target/i386/nvmm/meson.build
> > @@ -0,0 +1,4 @@
> > +i386_softmmu_ss.add(when: 'CONFIG_NVMM', if_true: files(
> > +  'nvmm-all.c',
> > +  'nvmm-accel-ops.c',
> > +))
> 
> The nvmm library should be added here.

I am not sure what you mean by that. You provided a patch for the meson.build
file, will that not suffice?

With regards,
Reinoud


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-04-01 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 20:07 [PATCH v6 0/4] Implements the NetBSD Virtual Machine Monitor accelerator Reinoud Zandijk
2021-03-31 20:07 ` [PATCH v6 1/4] Add NVMM accelerator: configure and build logic Reinoud Zandijk
2021-04-01  8:28   ` Paolo Bonzini
2021-04-01 12:17     ` Reinoud Zandijk
2021-04-01 12:44       ` Paolo Bonzini
2021-03-31 20:07 ` [PATCH v6 2/4] Add NVMM accelerator: x86 CPU support Reinoud Zandijk
2021-04-01  8:35   ` Paolo Bonzini
2021-04-01 12:32     ` Reinoud Zandijk [this message]
2021-04-01 12:48       ` Paolo Bonzini
2021-03-31 20:07 ` [PATCH v6 3/4] Add NVMM accelerator: acceleration enlightenments Reinoud Zandijk
2021-03-31 20:08 ` [PATCH v6 4/4] Add NVMM Accelerator: add maintainers for NetBSD/NVMM Reinoud Zandijk
2021-04-01  8:36 ` [PATCH v6 0/4] Implements the NetBSD Virtual Machine Monitor accelerator 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=YGW9ZSo5RbeqDuVX@diablo.13thmonkey.org \
    --to=reinoud@netbsd.org \
    --cc=ehabkost@redhat.com \
    --cc=kamil@NetBSD.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=ryoon@netbsd.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).