From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Erlon Cruz <Erlon.Cruz@fit-tecnologia.org.br>
Cc: Erlon Cruz <erlon.cruz@br.flextronics.com>,
David Gibson <david@gibson.dropbear.id.au>,
Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Enablig DLPAR capacity on QEMU pSeries
Date: Sat, 06 Oct 2012 06:56:26 +1000 [thread overview]
Message-ID: <1349470586.4260.75.camel@pasglop> (raw)
In-Reply-To: <AB3B4A2BF00C7341A4ADB28108160A9E02A26B86@AMSACEX4.americas.ad.flextronics.com>
On Fri, 2012-10-05 at 08:26 -0700, Erlon Cruz wrote:
> >
> > Why not add a proper RTAS and do this work there?
>
> The RTAS call is how the guest will communicate with the host. It
> doesn't have a way to get interrupted and notified about any changes.
> So
> to start the changing of something, the guest need some kind of
> trigger
I believe the question was more about where we put the resource
allocation.
The interrupt problem remains in any case yes, but inventing a new RTAT
event interrupt (or hijacking EPOW) isn't a big deal.
Cheers,
Ben.
next prev parent reply other threads:[~2012-10-05 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 14:54 [Qemu-devel] Enablig DLPAR capacity on QEMU pSeries Erlon Cruz
2012-09-12 15:53 ` Alexander Graf
2012-09-12 20:56 ` Erlon Cruz
2012-09-12 21:42 ` Alexander Graf
2012-09-12 21:48 ` Benjamin Herrenschmidt
2012-09-13 15:15 ` Erlon Cruz
2012-09-13 21:45 ` Benjamin Herrenschmidt
2012-10-05 14:08 ` Erlon Cruz
2012-10-05 14:42 ` Anthony Liguori
2012-10-05 15:26 ` Erlon Cruz
2012-10-05 20:56 ` Benjamin Herrenschmidt [this message]
2012-10-05 20:49 ` Benjamin Herrenschmidt
2012-10-06 14:54 ` David Gibson
2012-10-06 19:39 ` Benjamin Herrenschmidt
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=1349470586.4260.75.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Erlon.Cruz@fit-tecnologia.org.br \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=david@gibson.dropbear.id.au \
--cc=erlon.cruz@br.flextronics.com \
--cc=qemu-devel@nongnu.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.