On 14/04/15 11:33, Ian Campbell wrote:
>> Whoops. I didn't spot those one thanks.
>
> libxc is not ABI stable, we can make these bigger if necessary, or
> introduce new interface etc as required depending on how things pan out
> at the hypercall layer.
FIY, a patch has been sent on the ML see "[P
On Fri, 2015-04-03 at 15:31 +0200, Julien Grall wrote:
> > Also, as we plan to use passtrough, we there are such places:
>
> > In tools/libxc/include/xenctrl.h:
> > int xc_domain_bind_pt_irq(xc_interface *xch,
> >uint32_t domid,
> > *uint8_t* machine_irq,
> >
On 03/04/2015 14:40, Iurii Konovalenko wrote:
Hi, Ian! Hi, Julien!
Hi Iurii,
Thank you for your replies.
On Thu, Apr 2, 2015 at 6:19 PM, Ian Campbell mailto:ian.campb...@citrix.com>> wrote:
> Please can you give some example of this?
On Thu, Apr 2, 2015 at 6:34 PM, Julien Grall mailto:jul
Hi, Ian! Hi, Julien!
Thank you for your replies.
On Thu, Apr 2, 2015 at 6:19 PM, Ian Campbell
wrote:
> Please can you give some example of this?
On Thu, Apr 2, 2015 at 6:34 PM, Julien Grall
wrote:
> Can you give an example of files/structures using uint8_t for IRQ?
As Julien wrote, it is relate
(CC Stefano and Ian)
On 02/04/2015 16:05, Iurii Konovalenko wrote:
Hi, Julien!
Hello Iurii,
During bringing up Xen on Renesas Lager board we faced with problem.
A lot of Xen sources relies on statement, that IRQ number is less then
256 and variables, parameters, fields etc. are of type uint
On Thu, 2015-04-02 at 18:05 +0300, Iurii Konovalenko wrote:
> Hi, Julien!
>
> During bringing up Xen on Renesas Lager board we faced with problem.
> A lot of Xen sources relies on statement, that IRQ number is less then
> 256 and variables, parameters, fields etc. are of type uint8_t.
Please can
Hi, Julien!
During bringing up Xen on Renesas Lager board we faced with problem.
A lot of Xen sources relies on statement, that IRQ number is less then
256 and variables, parameters, fields etc. are of type uint8_t. But we
can have IRQs, that are greater then 255, for example on RCar H2 SoC.
Also,
