RE: [Xen-ia64-devel] IOSAPIC virtualisation

2006-02-09 Thread Dong, Eddie
Tristan Gingold wrote: Le Vendredi 03 Février 2006 17:13, Alex Williamson a écrit : On Fri, 2006-02-03 at 09:33 +0100, Tristan Gingold wrote: [...] I agree that we can't hit this problem right now, but it's easy to fix and would be one less thing we might miss when we do enable driver

Re: [Xen-ia64-devel] IOSAPIC virtualisation

2006-02-09 Thread Tristan Gingold
Le Jeudi 09 Février 2006 11:05, Dong, Eddie a écrit : Tristan Gingold wrote: Le Vendredi 03 Février 2006 17:13, Alex Williamson a écrit : On Fri, 2006-02-03 at 09:33 +0100, Tristan Gingold wrote: [...] I agree that we can't hit this problem right now, but it's easy to fix and would be

RE: [Xen-ia64-devel] IOSAPIC virtualisation

2006-02-09 Thread Dong, Eddie
Tristan Gingold wrote: Yes I have just copied from the original code. However, we should also take IPI into consideration (unless we go directly to event channel). Can you explain more on IPI stuff? I am not in the context. Anyway, keep the capability that a machine IRQ may be bound to

Re: [Xen-ia64-devel] IOSAPIC virtualisation

2006-02-03 Thread Tristan Gingold
Le Jeudi 02 Février 2006 19:16, Alex Williamson a écrit : Hi Tristan, I took another quick skim through and have a few more comments. It's looking good, thanks for all your work here! Alex On Thu, 2006-02-02 at 15:01 +0100, Tristan Gingold wrote: - *pval =

Re: [Xen-ia64-devel] iosapic virtualisation

2006-02-02 Thread Tristan Gingold
Le Mercredi 01 Février 2006 16:48, Alex Williamson a écrit : On Wed, 2006-02-01 at 10:11 +0100, Tristan Gingold wrote: Le Mardi 31 Janvier 2006 20:53, Alex Williamson a écrit : [...] * We need to paravirtualize reads of the IOSAPIC as well as writes. Since the IOSAPICs use

Re: [Xen-ia64-devel] IOSAPIC virtualisation

2006-02-02 Thread Alex Williamson
Hi Tristan, I took another quick skim through and have a few more comments. It's looking good, thanks for all your work here! Alex On Thu, 2006-02-02 at 15:01 +0100, Tristan Gingold wrote: - *pval = ia64_getreg(_IA64_REG_CR_LID); + *pval = vcpu-vcpu_id * 0x0101;

Re: [Xen-ia64-devel] iosapic virtualisation

2006-02-01 Thread Tristan Gingold
Le Mercredi 01 Février 2006 10:11, Tristan Gingold a écrit : Le Mardi 31 Janvier 2006 20:53, Alex Williamson a écrit : On Tue, 2006-01-31 at 12:29 +0100, Tristan Gingold wrote: [...] * The vector-to-rte lookup in xen_reflect_interrupt_to_domain() looks rather heavy weight. It

Re: [Xen-ia64-devel] iosapic virtualisation

2006-02-01 Thread Alex Williamson
On Wed, 2006-02-01 at 10:11 +0100, Tristan Gingold wrote: Le Mardi 31 Janvier 2006 20:53, Alex Williamson a écrit : * Assigning vectors as defined by the domain; I think this is covered by some of the comments included about future problems, but maybe we should

Re: [Xen-ia64-devel] iosapic virtualisation

2006-02-01 Thread Alex Williamson
On Wed, 2006-02-01 at 12:35 +0100, Tristan Gingold wrote: Le Mercredi 01 Février 2006 10:11, Tristan Gingold a écrit : Le Mardi 31 Janvier 2006 20:53, Alex Williamson a écrit : On Tue, 2006-01-31 at 12:29 +0100, Tristan Gingold wrote: [...] * The vector-to-rte lookup in

RE: [Xen-ia64-devel] iosapic virtualisation

2006-01-31 Thread Magenheimer, Dan (HP Labs Fort Collins)
Any other comments ? Sorry for the delay... I'm focused on trying to get xen-unstable.hg working for ia64 before the 3.0.1 freeze. Looks like Alex has provided some good comments... and he is far smarter about this part of the ia64 architecture than I am anyway! :-) Do you think it could be