All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Matt Redfearn <matt.redfearn@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	linux-mips@linux-mips.org, linux-remoteproc@vger.kernel.org,
	Lisa Parratt <lisa.parratt@imgtec.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Qais Yousef <qsyousef@gmail.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Lisa Parratt <Lisa.Parratt@imgtec.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Jason Cooper <jason@lakedaemon.net>,
	James Hogan <james.hogan@imgtec.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Paul Burton <paul.burton@imgtec.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v4 0/4] MIPS: Remote processor driver
Date: Wed, 9 Nov 2016 11:15:20 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1611091111041.3501@nanos> (raw)
In-Reply-To: <1478103063-17653-1-git-send-email-matt.redfearn@imgtec.com>

On Wed, 2 Nov 2016, Matt Redfearn wrote:
> The MIPS remote processor driver allows non-Linux firmware to take
> control of and execute on one of the systems VPEs. The CPU must be
> offlined from Linux first. A sysfs interface is created which allows
> firmware to be loaded and changed at runtime. A full description is
> available at [1]. An example firmware that can be used with this driver
> is available at [2].
> 
> This is useful to allow running bare metal code, or an RTOS, on one or
> more CPUs while allowing Linux to continue running on those remaining.

And how is actually guaranteed that these two things are properly seperated
(memory, devices, interrupts etc.) ?

We have rejected attempts to do exactly the same thing on x86 in the
past. There is virtualization and NOHZ_FULL to do it proper and not just
with a horrible hackery.

Thanks,

	tglx

  parent reply	other threads:[~2016-11-09 10:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 16:10 [PATCH v4 0/4] MIPS: Remote processor driver Matt Redfearn
2016-11-02 16:10 ` Matt Redfearn
2016-11-02 16:11 ` [PATCH v4 1/4] irqchip: mips-gic: Add context saving for MIPS_REMOTEPROC Matt Redfearn
2016-11-02 16:11   ` Matt Redfearn
2016-11-02 16:11 ` [PATCH v4 2/4] MIPS: CPS: Add VP(E) stealing Matt Redfearn
2016-11-02 16:11   ` Matt Redfearn
2016-11-02 16:11 ` [PATCH v4 3/4] remoteproc/MIPS: Add a remoteproc driver for MIPS Matt Redfearn
2016-11-02 16:11   ` Matt Redfearn
2016-11-02 16:11 ` [PATCH v4 4/4] MIPS: Deprecate VPE Loader Matt Redfearn
2016-11-02 16:11   ` Matt Redfearn
2016-11-03 10:12   ` Sergei Shtylyov
2016-11-09 10:15 ` Thomas Gleixner [this message]
2016-11-09 13:30   ` [PATCH v4 0/4] MIPS: Remote processor driver Matt Redfearn
2016-11-09 13:30     ` Matt Redfearn
2016-11-09 14:16     ` Thomas Gleixner

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=alpine.DEB.2.20.1611091111041.3501@nanos \
    --to=tglx@linutronix.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=james.hogan@imgtec.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=lisa.parratt@imgtec.com \
    --cc=marc.zyngier@arm.com \
    --cc=matt.redfearn@imgtec.com \
    --cc=ohad@wizery.com \
    --cc=paul.burton@imgtec.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=peterz@infradead.org \
    --cc=qsyousef@gmail.com \
    --cc=ralf@linux-mips.org \
    --cc=yamada.masahiro@socionext.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.