[Xen-ia64-devel] [PATCH] remove printk warning of xen_init

2006-04-12 Thread Isaku Yamahata
remove printk warning of xen_init -- yamahata # HG changeset patch # User [EMAIL PROTECTED] # Node ID 3613df53207efcecfe51c1972db00497d2d8a3f2 # Parent 5cc367720223d06e5ec420da387218f46c9ed8e9 remove printk warning of xen_init PATCHNAME: remove_printk_warning_of_xen_init Signed-off-by: Isaku Y

[Xen-ia64-devel] [PATCH] call setup_xen_feature()

2006-04-12 Thread Isaku Yamahata
add setup_xen_features() call to setup_arch() in xenLinux/ia64 Now features.c is compiled into xenLinux/ia64 for xen_feature(), but it is not initialized. xenLinux/x86 calls xetup_xen_features() from setup_arch(). PATCHNAME: add_setup_xen_features_call_to_setup_arch_of_ia64 -- yamahata # HG chan

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Xu, Anthony
>From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Alex >Williamson >Sent: 2006?4?12? 23:29 >To: Tristan Gingold >Cc: Isaku Yamahata; xen-ia64-devel@lists.xensource.com >Subject: Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches > >On Wed, 2006-04-12 at 09:01 +0100, Tristan

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tian, Kevin
>From: Alex Williamson [mailto:[EMAIL PROTECTED] >Sent: 2006年4月12日 23:29 > >On Wed, 2006-04-12 at 09:01 +0100, Tristan Gingold wrote: > >> > Last, the only way to prevent such io access is from guest itself, >> > meant not compiling native drivers in. Or else there's no way for >> > xen to handle i

RE: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64

2006-04-12 Thread Tian, Kevin
>From: Alex Williamson [mailto:[EMAIL PROTECTED] >Sent: 2006年4月13日 4:51 > >On Wed, 2006-04-12 at 15:49 +0800, Tian, Kevin wrote: >> >> In a word, there's no easy way to tune performance as long as >> interrupts and events are still strictly split into two groups as I >> mentioned in last mail.

RE: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64

2006-04-12 Thread Alex Williamson
On Wed, 2006-04-12 at 15:49 +0800, Tian, Kevin wrote: > > In a word, there's no easy way to tune performance as long as > interrupts and events are still strictly split into two groups as I > mentioned in last mail. You always lose one side. However once the > final event layer is ready (sho

[Xen-ia64-devel] [PATCH] no need to build x86 firmware

2006-04-12 Thread Al Stone
In the tools part of xen, if you have bcc installed, 'make tools' will try to compile all of the x86 firmware (ACPI, ROM BIOS, VGA BIOS). This patch turns that off if we're building for ia64, where we don't really need it. Signed-off-by: Al Stone <[EMAIL PROTECTED]> -- Ciao, al

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Alex Williamson
On Wed, 2006-04-12 at 09:01 +0100, Tristan Gingold wrote: > > Last, the only way to prevent such io access is from guest itself, > > meant not compiling native drivers in. Or else there's no way for > > xen to handle it correctly. > User should disable drivers in domU. Everybody agree with that!

Re: single software TLB vs. multiple software TLBs (was RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb)

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 16:51, Dong, Eddie a écrit : > Tristan Gingold wrote: > >> Just make sure I am understanding correctly. With the help of > >> software TLB for guest huge translation, you have the flexibility to > >> either breakdown it into smaller ones to VHPT for all entries at a > >> t

RE: single software TLB vs. multiple software TLBs (was RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb)

2006-04-12 Thread Dong, Eddie
Tristan Gingold wrote: >> >> Just make sure I am understanding correctly. With the help of >> software TLB for guest huge translation, you have the flexibility to >> either breakdown it into smaller ones to VHPT for all entries at a >> time, or you can do one at a time. Defenitely several at a tim

[Xen-ia64-devel] Re: [Xen-devel] [PATCH 4/6] grantable and address conversion patches

2006-04-12 Thread Isaku Yamahata
I attached the updated patch. On Mon, Apr 10, 2006 at 01:47:20PM +0100, Keir Fraser wrote: > > On 10 Apr 2006, at 13:37, Isaku Yamahata wrote: > > >>I'd rather define a function to fill in the entire structure in > >>gnttab.h. > > > >I hope that the attached patch is much more preferable > >tha

Re: [Xen-ia64-devel] xen-ia64-unstable.hg seems broken.

2006-04-12 Thread Aron Griffis
Aron Griffis wrote: [Wed Apr 12 2006, 08:14:49AM EDT] > Broken for me, but without details I can't confirm it's the same thing > you're seeing. Here is what I get on pull: It seems that a new clone sorted things out for me. This might have been related to updating to mercurial-0.8.1 Aron

Re: [Xen-ia64-devel] xen-ia64-unstable.hg seems broken.

2006-04-12 Thread Aron Griffis
Tristan Gingold wrote: [Wed Apr 12 2006, 07:45:17AM EDT] > the current changeset (9675) seems broken. Confirmation ? Broken for me, but without details I can't confirm it's the same thing you're seeing. Here is what I get on pull: $ hg pull pulling from http://xenbits.xensource.com/ext

Re: [Xen-ia64-devel] xen-ia64-unstable.hg seems broken.

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 13:43, Zhang, Xiantao a écrit : > Hi Tristan, > I am using CSet9675 now. It should be OK with me :) Oops, sorry it's me :-( Tristan. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensour

RE: [Xen-ia64-devel] xen-ia64-unstable.hg seems broken.

2006-04-12 Thread Zhang, Xiantao
Hi Tristan, I am using CSet9675 now. It should be OK with me :) Thanks -Xiantao > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tristan > Gingold > Sent: 2006年4月12日 19:45 > To: xen-ia64-devel@lists.xensource.com > Subject: [Xen-ia64-devel] x

[Xen-ia64-devel] xen-ia64-unstable.hg seems broken.

2006-04-12 Thread Tristan Gingold
Hi, the current changeset (9675) seems broken. Confirmation ? Tristan. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel

Re: single software TLB vs. multiple software TLBs (was RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb)

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 11:41, Dong, Eddie a écrit : > Tristan Gingold wrote: > > Le Mercredi 12 Avril 2006 10:57, Dong, Eddie a écrit : > >> Tristan: > >>You are probably avocating for the flexibility of hash TLB too from > >> the issue :-) Yes, when multiple TLBs are supported, i.e. hash TL

RE: single software TLB vs. multiple software TLBs (was RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb)

2006-04-12 Thread Dong, Eddie
Tristan Gingold wrote: > Le Mercredi 12 Avril 2006 10:57, Dong, Eddie a écrit : >> Tristan: >> You are probably avocating for the flexibility of hash TLB too from >> the issue :-) Yes, when multiple TLBs are supported, i.e. hash TLB >> here, those big guest page translations can be put into so

Re: single software TLB vs. multiple software TLBs (was RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb)

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 10:57, Dong, Eddie a écrit : > Tristan: > You are probably avocating for the flexibility of hash TLB too from the > issue :-) Yes, when multiple TLBs are supported, i.e. hash TLB here, those > big guest page translations can be put into software TLB using gmfn (leave

Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 10:53, Xu, Anthony a écrit : > From: Tristan Gingold > > >Sent: 2006年4月12日 16:38 > >To: Xu, Anthony; xen-ia64-devel@lists.xensource.com > >Subject: Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb > > > >Le Mercredi 12 Avril 2006 10:01, Xu, Anthony a écrit : > >> From

single software TLB vs. multiple software TLBs (was RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb)

2006-04-12 Thread Dong, Eddie
Tristan: You are probably avocating for the flexibility of hash TLB too from the issue :-) Yes, when multiple TLBs are supported, i.e. hash TLB here, those big guest page translations can be put into software TLB using gmfn (leave to future tuning). When it is inserted into machi

RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb

2006-04-12 Thread Xu, Anthony
>From: Tristan Gingold >Sent: 2006年4月12日 16:38 >To: Xu, Anthony; xen-ia64-devel@lists.xensource.com >Subject: Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb > >Le Mercredi 12 Avril 2006 10:01, Xu, Anthony a écrit : >> From: Tristan Gingold [mailto:[EMAIL PROTECTED] >> >> >Sent: 2006年4月12日 15

Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 10:01, Xu, Anthony a écrit : > From: Tristan Gingold [mailto:[EMAIL PROTECTED] > > >Sent: 2006年4月12日 15:53 > >To: Xu, Anthony; xen-ia64-devel@lists.xensource.com > >Subject: Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb > > > >Le Vendredi 07 Avril 2006 21:02, Xu, A

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 10:09, Tian, Kevin a écrit : > From: Tristan Gingold [mailto:[EMAIL PROTECTED] > > >Sent: 2006年4月12日 16:02 > > > >> First, current code is taking mfn 0 as the result when mapping is not > >> found which is more problematic like write access as you mentioned > >> > >> Secon

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tian, Kevin
>From: Tristan Gingold [mailto:[EMAIL PROTECTED] >Sent: 2006年4月12日 16:02 >> >> First, current code is taking mfn 0 as the result when mapping is not >> found which is more problematic like write access as you mentioned >> >> Second, mapping to a dummy page has similar effect, but no harm >> for wri

RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb

2006-04-12 Thread Xu, Anthony
>From: Tristan Gingold [mailto:[EMAIL PROTECTED] >Sent: 2006年4月12日 15:53 >To: Xu, Anthony; xen-ia64-devel@lists.xensource.com >Subject: Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb > >Le Vendredi 07 Avril 2006 21:02, Xu, Anthony a écrit : >> Hash vTLB is intended to address SMP scalability

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 09:23, Tian, Kevin a écrit : > From: Tristan Gingold [mailto:[EMAIL PROTECTED] [...] > >> >> >But this issues isn't specific to the P2M/VP patch. > >> > > >> >I don't agree with this solution. I really prefer to have warnings > >> > because it > >> >means something got wr

RE: [Xen-ia64-devel] [PATCH] Add event callback for xen/ia64

2006-04-12 Thread Tian, Kevin
Hi, Alex, Following is the data I collected which is similar to yours. I have domU memory 512M configured, and the absolute values below are different due to hardware difference but relative comparison result is similar: [By wget, 3 experiments] Before applying event patch: Dom0 wget:

Re: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb

2006-04-12 Thread Tristan Gingold
Le Vendredi 07 Avril 2006 21:02, Xu, Anthony a écrit : > Hash vTLB is intended to address SMP scalability for large system. If I understand correctly, the Hash vTLB patch doesn't handle itc whose ps > rr.ps (there is a panic here). After a few minutes of thinking, I don't see how this could be do

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tian, Kevin
>From: Tristan Gingold [mailto:[EMAIL PROTECTED] >Sent: 2006年4月12日 15:20 > >Le Mercredi 12 Avril 2006 09:07, Tian, Kevin a écrit : >> From: Tristan Gingold [mailto:[EMAIL PROTECTED] >> >> >Sent: 2006年4月12日 15:08 >> > >> >Le Mercredi 12 Avril 2006 08:12, Tian, Kevin a écrit : >> >> From: Isaku Yamah

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 09:07, Tian, Kevin a écrit : > From: Tristan Gingold [mailto:[EMAIL PROTECTED] > > >Sent: 2006年4月12日 15:08 > > > >Le Mercredi 12 Avril 2006 08:12, Tian, Kevin a écrit : > >> From: Isaku Yamahata [mailto:[EMAIL PROTECTED] > > > >[...] > > > >> >That's an access to keyboard

Re: [Xen-ia64-devel] "xend start" is slow on top of p2m patch

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 09:11, Tian, Kevin a écrit : > Hi, Isaku, > Not sure whether you also observed same phenomenon where > "xend start" will halt 4~5 seconds to complete. Is there some heavy > weight operations at that time? May not related to your patch, but > it's the first time for m

[Xen-ia64-devel] "xend start" is slow on top of p2m patch

2006-04-12 Thread Tian, Kevin
Hi, Isaku, Not sure whether you also observed same phenomenon where "xend start" will halt 4~5 seconds to complete. Is there some heavy weight operations at that time? May not related to your patch, but it's the first time for me to see it. Yesterday on latest tip, it still works well.

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tian, Kevin
>From: Tristan Gingold [mailto:[EMAIL PROTECTED] >Sent: 2006年4月12日 15:08 >Le Mercredi 12 Avril 2006 08:12, Tian, Kevin a écrit : >> From: Isaku Yamahata [mailto:[EMAIL PROTECTED] >[...] >> >That's an access to keyboard port possibly because now xen0/xenU >> > >> >> is compiled as one image with mor

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Dong, Eddie
Congratulations! That is why Kevin and I advocated many times before to suggest p2m translation (p!=m) :-) Can we also share the free beer? Eddie Magenheimer, Dan (HP Labs Fort Collins) wrote: > I was also able to get networking working with Isaku's patches > and Alex's. Hooray! For the last ei

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

2006-04-12 Thread Tristan Gingold
Le Mercredi 12 Avril 2006 08:12, Tian, Kevin a écrit : > From: Isaku Yamahata [mailto:[EMAIL PROTECTED] [...] > >That's an access to keyboard port possibly because now xen0/xenU > > > >> is compiled as one image with more drivers added. Maybe it's better > >> for us to map all 64M mmio area of domU