On Mon, Apr 13, 2015 at 11:46:36AM +0100, Mark Rutland wrote:
Hi,
Otherwise the is_guest() function would be many if-else statements
trying to determine the type of guest it is before it even knows that
it is a guest.
It's worth noting that to some extent this may always be
On Thu, Apr 09, 2015 at 01:06:47PM +0100, Andrew Jones wrote:
On Thu, Apr 09, 2015 at 08:57:23AM +0100, Marc Zyngier wrote:
On Thu, 9 Apr 2015 02:46:54 +0100
Mario Smarduch m.smard...@samsung.com wrote:
Hi Mario,
I'm working with AsyncPF, and currently using
hyp call to
On Thu, Apr 09, 2015 at 03:00:27PM +0100, Mark Rutland wrote:
While the HVC immediate could be used to distinguish different types of
calls, the guest still needs to first determine that issuing a HVC is
not going to bring down the system, which requires it to know that a
suitable
On Thu, Apr 09, 2015 at 03:59:46PM +0200, Andrew Jones wrote:
On Thu, Apr 09, 2015 at 03:35:06PM +0200, Christoffer Dall wrote:
On Thu, Apr 09, 2015 at 02:06:47PM +0200, Andrew Jones wrote:
On Thu, Apr 09, 2015 at 08:57:23AM +0100, Marc Zyngier wrote:
On Thu, 9 Apr 2015 02:46:54 +0100
For example, if Windows guests were taught to look for a particular
ACPI table to learn about their HyperV features, then KVM could fake
that table and also emulate the hypercalls.
This requires KVM to provide those services and for the information to
be in the appropriate
I'm working with AsyncPF, and currently using
hyp call to communicate guest GFN for host to inject
virtual abort - page not available/page available.
Currently only PSCI makes use of that interface,
(handle_hvc()) can we overload interface with additional
hyp calls in this case pass guest gfn?
