All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: will@kernel.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: [PATCH kvmtool v7 1/3] aarch64: Populate the vCPU struct before target->init()
Date: Wed, 02 Mar 2022 14:21:20 +0000	[thread overview]
Message-ID: <874k4g3067.wl-maz@kernel.org> (raw)
In-Reply-To: <20220302140734.1015958-2-sebastianene@google.com>

On Wed, 02 Mar 2022 14:07:33 +0000,
Sebastian Ene <sebastianene@google.com> wrote:
> 
> Move the vCPU structure initialisation before the target->init() call to
>  keep a reference to the kvm structure during init().
> This is required by the pvtime peripheral to reserve a memory region
> while the vCPU is beeing initialised.
> 
> Signed-off-by: Sebastian Ene <sebastianene@google.com>

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: kvm@vger.kernel.org, qperret@google.com,
	kvmarm@lists.cs.columbia.edu, will@kernel.org,
	julien.thierry.kdev@gmail.com
Subject: Re: [PATCH kvmtool v7 1/3] aarch64: Populate the vCPU struct before target->init()
Date: Wed, 02 Mar 2022 14:21:20 +0000	[thread overview]
Message-ID: <874k4g3067.wl-maz@kernel.org> (raw)
In-Reply-To: <20220302140734.1015958-2-sebastianene@google.com>

On Wed, 02 Mar 2022 14:07:33 +0000,
Sebastian Ene <sebastianene@google.com> wrote:
> 
> Move the vCPU structure initialisation before the target->init() call to
>  keep a reference to the kvm structure during init().
> This is required by the pvtime peripheral to reserve a memory region
> while the vCPU is beeing initialised.
> 
> Signed-off-by: Sebastian Ene <sebastianene@google.com>

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2022-03-02 14:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 14:07 [PATCH kvmtool v7 0/3] aarch64: Add stolen time support Sebastian Ene
2022-03-02 14:07 ` Sebastian Ene
2022-03-02 14:07 ` [PATCH kvmtool v7 1/3] aarch64: Populate the vCPU struct before target->init() Sebastian Ene
2022-03-02 14:07   ` Sebastian Ene
2022-03-02 14:21   ` Marc Zyngier [this message]
2022-03-02 14:21     ` Marc Zyngier
2022-03-02 14:07 ` [PATCH kvmtool v7 2/3] aarch64: Add stolen time support Sebastian Ene
2022-03-02 14:07   ` Sebastian Ene
2022-03-02 14:41   ` Marc Zyngier
2022-03-02 14:41     ` Marc Zyngier
2022-03-03 12:01     ` Sebastian Ene
2022-03-03 17:51       ` Marc Zyngier
2022-03-07 11:46         ` Sebastian Ene
2022-03-07 10:52     ` Alexandru Elisei
2022-03-07 10:52       ` Alexandru Elisei
2022-03-07 11:46   ` Alexandru Elisei
2022-03-07 11:46     ` Alexandru Elisei
2022-03-07 14:55     ` Sebastian Ene
2022-03-02 14:07 ` [PATCH kvmtool v7 3/3] Add --no-pvtime command line argument Sebastian Ene
2022-03-02 14:07   ` Sebastian Ene

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=874k4g3067.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=sebastianene@google.com \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.