On 05/29/2013 06:57:32 PM, Benjamin Herrenschmidt wrote:
On Wed, 2013-05-29 at 18:38 -0500, Scott Wood wrote:
> > Yes. I'd like to have them in. Their implementation is actually
fairly
> > trivial and they cannot be emulated by qemu if the rest of the
XICS is
> > in the kernel, so it's a pr
On Wed, 2013-05-29 at 18:38 -0500, Scott Wood wrote:
> > Yes. I'd like to have them in. Their implementation is actually fairly
> > trivial and they cannot be emulated by qemu if the rest of the XICS is
> > in the kernel, so it's a problem.
>
> OK. Does it make more sense for you to take it as P
On 05/28/2013 07:41:18 PM, Benjamin Herrenschmidt wrote:
On Tue, 2013-05-28 at 12:41 -0500, Scott Wood wrote:
> I believe Alex is staying far away from e-mail on his vacation.
He's
> asked me to fill in for him while he's gone.
>
> The patch itself seems reasonable (though I don't know much
On Tue, 2013-05-28 at 12:41 -0500, Scott Wood wrote:
> I believe Alex is staying far away from e-mail on his vacation. He's
> asked me to fill in for him while he's gone.
>
> The patch itself seems reasonable (though I don't know much about XICS,
> and do have one question...), but I'll leav
On 05/23/2013 08:42:21 PM, Paul Mackerras wrote:
This adds the remaining two hypercalls defined by PAPR for
manipulating
the XICS interrupt controller, H_IPOLL and H_XIRR_X. H_IPOLL returns
information about the priority and pending interrupts for a virtual
cpu, without changing any state. H_
This adds the remaining two hypercalls defined by PAPR for manipulating
the XICS interrupt controller, H_IPOLL and H_XIRR_X. H_IPOLL returns
information about the priority and pending interrupts for a virtual
cpu, without changing any state. H_XIRR_X is like H_XIRR in that it
reads and acknowledg
