From: Nishanth Menon <nm@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Tero Kristo <t-kristo@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: [RFC PATCH 1/3] Documentation: dt: keystone: ti-sci: Add optional host-id parameter
Date: Tue, 12 Jun 2018 17:09:18 -0500 [thread overview]
Message-ID: <20180612220918.7cchihtcmmta6pm5@kahuna> (raw)
In-Reply-To: <20180612213922.GA26791@rob-hp-laptop>
On 21:39-20180612, Rob Herring wrote:
> On Tue, Jun 05, 2018 at 01:26:38AM -0500, Nishanth Menon wrote:
> > Texas Instrument's System Control Interface (TISCI) permits the
> > ability for Operating Systems to running in virtual machines to be
>
> ...for OSs running in virtual...
Ack. thanks.
>
> > able to independently communicate with the firmware without the need
> > going through an hypervisor.
> >
> > The "host-id" in effect is the hardware representation of the
> > host (example: VMs locked to a core) as identified to the System
> > Controller.
>
> So the hypervisor will fill in host-id's for each VM instance?
Yes OR have it's own device tree blobs representation of it's own host
IDs assigned by system firmware. This provides complete independence of
VMs to communicate with the system controller (once the host-id is
provided) without switching to hyp for arbitration (and yes, verified
ability with jailhouse hypervisor and multiple linux instances operating
simultaneously). This also has the added benefit of:
1. The burden of hypervisor from being involved in PM functionality as each
of the VMs can operate autonomously.
2. In TI SoCs which are heterogeneous, the system firmware plays the role
of system master communicating with multiple firmware(running on various
uCs) and OSes running on bigger cores.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2018-06-12 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 6:26 [RFC PATCH 0/3] firmware: Add K3 Support for TISCI driver Nishanth Menon
2018-06-05 6:26 ` [RFC PATCH 1/3] Documentation: dt: keystone: ti-sci: Add optional host-id parameter Nishanth Menon
2018-06-12 21:39 ` Rob Herring
2018-06-12 22:09 ` Nishanth Menon [this message]
2018-06-05 6:26 ` [RFC PATCH 2/3] firmware: ti_sci: Provide host-id as an optional dt parameter Nishanth Menon
2018-06-05 6:26 ` [RFC PATCH 3/3] arm64: dts: ti: k3-am6: Add Device Management Security Controller support Nishanth Menon
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=20180612220918.7cchihtcmmta6pm5@kahuna \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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