From: Sudeep Holla <sudeep.holla@arm.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
Marc Bonnici <marc.bonnici@arm.com>,
Olivier Deprez <Olivier.Deprez@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Bertrand Marquis <Bertrand.Marquis@arm.com>
Subject: Re: [PATCH v2 0/3] firmware: arm_ffa: Add support to run inside a guest/VM under a hypervisor
Date: Thu, 11 Apr 2024 15:30:14 +0100 [thread overview]
Message-ID: <Zhfz9tLO0Z4hkj9T@bogus> (raw)
In-Reply-To: <CAHUa44HBS_HqnRrNjYh+nELHx0NyB6CoX-fZEBGyB_Z3=QSTaQ@mail.gmail.com>
On Thu, Apr 11, 2024 at 03:30:41PM +0200, Jens Wiklander wrote:
> Hi Sudeep,
>
> On Thu, Apr 11, 2024 at 2:57 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > Add support for running the driver inside a guest/VM under a hypervisor.
> >
> > The main difference include:
> > 1. supporting introducing notification pending interrupt and
> > 2. Avoiding creation of all the notification bitmaps as they must be
> > created by the hypervisor before the VM is initialised
> >
> > The guest may need to use a notification pending interrupt instead of
> > or in addition to the schedule receiver interrupt.
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> > Hi Jens,
> >
> > This is almost identical to you single patch now. Just split into
> > 3 patches with refactoring kept separate. Can you please check if
> > this continues to work on your setup(unlikely to break anything).
> > Once you confirm, I am happy to queue it.
>
> Works for me:
> Tested-by: Jens Wiklander <jens.wiklander@linaro.org>
>
Thanks !
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-11 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 12:57 [PATCH v2 0/3] firmware: arm_ffa: Add support to run inside a guest/VM under a hypervisor Sudeep Holla
2024-04-11 12:57 ` [PATCH v2 1/3] firmware: arm_ffa: Skip creation of the notification bitmaps Sudeep Holla
2024-04-12 10:42 ` Sebastian Ene
2024-04-12 11:31 ` Sudeep Holla
2024-04-11 12:57 ` [PATCH v2 2/3] firmware: arm_ffa: Refactor SRI handling in prepartion to add NPI support Sudeep Holla
2024-04-11 12:57 ` [PATCH v2 3/3] firmware: arm_ffa: Add support for handling notification pending interrupt(NPI) Sudeep Holla
2024-04-11 13:30 ` [PATCH v2 0/3] firmware: arm_ffa: Add support to run inside a guest/VM under a hypervisor Jens Wiklander
2024-04-11 14:30 ` Sudeep Holla [this message]
2024-04-18 10:01 ` Sudeep Holla
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=Zhfz9tLO0Z4hkj9T@bogus \
--to=sudeep.holla@arm.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Olivier.Deprez@arm.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=marc.bonnici@arm.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 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.