[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH][RESEND]RE: [Xen-devel] [PATCH] Allow for arch specific VIRQs


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Fri, 28 Apr 2006 09:39:14 +0800
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 27 Apr 2006 18:39:47 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcZqAdbM9JeSHKRVRzWqQhJvBQNsfgAYk6kA
  • Thread-topic: [PATCH][RESEND]RE: [Xen-devel] [PATCH] Allow for arch specific VIRQs

>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2006年4月27日 21:48
>
>On 27 Apr 2006, at 14:40, Tian, Kevin wrote:
>
>> Allow for arch specific virq definition.
>>
>> IA64 arch defines some more percpu events, like perfmon
>> and MCA (Machine Check Abort), which can be categorized
>> into VIRQ type since generated by xen just like virtual
>> timer. Though I've not tidy up more types to be really
>> added, this patch first gives chance.
>
>The way you've defined it makes it hard to add more base virqs (as that
>would shift the arch-specific virq numbers, which is unacceptable as
>they are visible to guests). How about doing as for hypercalls and
>define VIRQ_ARCH_0...VIRQ_ARCH_7 as virqs 16-23, say?
>
>  -- Keir

Oops, I forgot the backward compatibility. Attached is the updated patch.

Signed-off-by Kevin Tian <kevin.tian@xxxxxxxxx>

Thanks,
Kevin

Attachment: arch_virq.patch
Description: arch_virq.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.