Fix of C/S 10529:4260eb8c08740de081c61a6237ffcb95b2d5 for IA64.
When page is zapped from a domain, the page referenced counter
is checked. But it results in false positive alert on Xen/IA64
because a page 'in use' has reference count 2 on Xen/IA64.
- a page is assigned to guest domain's psudo
Hi Aron,
Could you share me the current status for fedora-xen-ia64? Through your
mails, I see we should focus our efforts on linux-2.6-xen-fedora. But when I
applied the patch 199684 on it, conflicts occurs. Do you have any suggestion
for contributing to Fedora ?
Thanks Best Regards
This patch intends to remove the confusing flag ARCH_VMX_CONTIG_MEM for
VTi. It was used for indicating that VTi needs contiguous memory.
Currently, it seems useless. In addition, add the flag ARCH_VMX_DOMAIN
to ensure VMX_DOMAIN check correctly with all vcpus.
Thanks Best Regards
-Xiantao
hi,guys.
I guess it
may seempretty much weird. I am not sure if 32bit OS such as 32bit Red Hat
Linux distribution can run at xen-ia64?
I really
appreciate any suggestion, thanks a million.
Tom
___
Xen-ia64-devel mailing list
Hi Tom,
Currently, 32 bit
OS couldn’t be run on xen-ia64 due to different architectures between IA32
and IA64. 32 bit application should work well in 64 bit guest with BT
technology.
Anyway, your idea is very
good. Maybe somebody will implement it in future.
Thanks Best Regards
Hi, Tom
Xen-ia64 support only ia64 OS.
Xen-x86_64 can support both x86_64 OS and x86_32 OS.
Best Regards,
Akio Takebe
hi,guys.
I guess it may seem pretty much weird. I am not sure if 32bit OS such as
32bit Red Hat Linux distribution can run at xen-ia64?
I really appreciate any
Hi,
this is the first patch for drivers domains. With this patch and another one
for pcifront, I was able to use an ethernet card in a domU.
This patch adds the IOPORT_PERMISSION hypercall (with no effects other than
setting the rangeset), checks iomem caps and provides a more flexible way to
Le Jeudi 27 Juillet 2006 10:01, Isaku Yamahata a écrit :
It seems that you are right.
Probably I was somewhat confused at that time.
It seems everybody was confused ;-)
Tristan.
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
Hi, Tristan
Yes, but current VMX_DOMAIN check based on vcpu, so I think we had
better set a flag in arch_vcpu for convenience or change VMX_DOMAIN
implementation. Am I right?
Thanks Best Regards
-Xiantao
OTC,Intel Corporation
-Original Message-
From: Tristan Gingold
Hi Akio,
Thank you for your information. I am using the CSet34705 which should
be latest, and do you mean I should apply Aron's patches on it. right? In
addition, what's status about it?
BTW,
Thanks Best Regards
-Xiantao
OTC,Intel Corporation
-Original Message-
From:
Le Jeudi 27 Juillet 2006 11:05, Zhang, Xiantao a écrit :
Hi, Tristan
Yes, but current VMX_DOMAIN check based on vcpu, so I think we had
better
set a flag in arch_vcpu for convenience or change VMX_DOMAIN
implementation. Am I right? Thanks Best Regards
Oh yes, I missed the point.
Hi,
this patch ports pcifont to ia64. pciback compiles without any change.
I had to make a few change because pcifront use its own structure
(struct pcifront_sd) for sysdata while ia64 wants it own (at least for
pcibios_fixup_bus). My solution is to reuse the ia64 sysdata structure
for
Very clear now! Thank you very much.
-Xiantao
OTC,Intel Corporation
-Original Message-
From: Akio Takebe [mailto:[EMAIL PROTECTED]
Sent: 2006年7月27日 17:36
To: Zhang, Xiantao; Aron Griffis; Juan Quintela
Cc: Prarit Bhargava; [EMAIL PROTECTED]; Chris Wright;
[EMAIL PROTECTED];
Hi
I will report a new issue, which was found by Yongkang at first.
As already reported by Yongkang, we also met the same dom0-smp issue.
Our test environment is as below.
cset :10700
physical CPUs :3 (2 cores)
HyperThred:enable
We tried 3 patterns of tests.
The first testing was
Le Jeudi 27 Juillet 2006 12:23, yo.fujita a écrit :
Hi
I will report a new issue, which was found by Yongkang at first.
As already reported by Yongkang, we also met the same dom0-smp issue.
Our test environment is as below.
Thank you for the report. I will try to understand the issue.
Le Jeudi 27 Juillet 2006 12:23, yo.fujita a écrit :
Hi
I will report a new issue, which was found by Yongkang at first.
As already reported by Yongkang, we also met the same dom0-smp issue.
Our test environment is as below.
cset :10700
physical CPUs :3 (2 cores)
HyperThred
Hi.
On Thu, Jul 27, 2006 at 05:43:36PM +0800, You, Yongkang wrote:
Other Issue:
1. SMP_VTI_Boot may stop to boot after Calibrating delay loop...
I'm seeing a similar issue.
My case is UP VTI domain. VTI domain doesn't share pcpu with dom0.
FWIW
- vITV
By
On Thu, Jul 27, 2006 at 01:01:15PM +0200, Tristan Gingold wrote:
I have juest tried on a tiger4 4 cpus, with dom0_max_vcpus=8. The 8 cpus
started.
Did you increase CONFIG_NR_CPUS of your linux dot config?
--
yamahata
___
Xen-ia64-devel mailing
Le Jeudi 27 Juillet 2006 13:16, Isaku Yamahata a écrit :
On Thu, Jul 27, 2006 at 01:01:15PM +0200, Tristan Gingold wrote:
I have juest tried on a tiger4 4 cpus, with dom0_max_vcpus=8. The 8 cpus
started.
Did you increase CONFIG_NR_CPUS of your linux dot config?
Its value is 8.
If this is
On 27 Jul 2006, at 10:41, Tristan Gingold wrote:
this patch ports pcifont to ia64. pciback compiles without any change.
I had to make a few change because pcifront use its own structure
(struct pcifront_sd) for sysdata while ia64 wants it own (at least for
pcibios_fixup_bus). My solution is
Hi,
this patch allows IO ports to be mapped/unmapped in domU.
Using it I was able to mount a usb-key in domU.
Tristan.
# HG changeset patch
# User [EMAIL PROTECTED]
# Node ID d7bb72ade3d3adfca6dff3a43b04fd19fa3541d6
# Parent 1ffb1200700b08420a1656b817171798ff45bad4
IO ports for driver domains.
Le Jeudi 27 Juillet 2006 14:12, Keir Fraser a écrit :
On 27 Jul 2006, at 10:41, Tristan Gingold wrote:
this patch ports pcifont to ia64. pciback compiles without any change.
I had to make a few change because pcifront use its own structure
(struct pcifront_sd) for sysdata while ia64
2006/7/21, Tristan Gingold [EMAIL PROTECTED]:
Le Vendredi 21 Juillet 2006 15:50, Rodrigo Lord a écrit : Hi! I`m testing xen-ia64 on an Itanium2 rx2600 (hp integrity) with 4 processors. but an error shows some times (in vm01 and dom0 too):
kernel unaligned access to 0xe0005ec2201e,
Hi,
debug message to be removed.
Tested by compiling.
Tristan.
# HG changeset patch
# User [EMAIL PROTECTED]
# Node ID b57145901e732be16f51f33191fe444621de160f
# Parent 4519e440e05c4083ce28187dd771416a31fbeda1
Cleanup: remove a debugging message.
Signed-off-by: Tristan Gingold [EMAIL
Hi,
some macros were lost. Re-add them.
ivt.S definitly needs cleanup!
Tested by booting dom0+domU.
Tristan.
# HG changeset patch
# User [EMAIL PROTECTED]
# Node ID c8fbf705c8dc1b05c1898830fda9f8ed57b2d609
# Parent b57145901e732be16f51f33191fe444621de160f
Include asm/vhpt.h to define
Xiantao and Akio,
Sorry that I'm not very good sharing status. Here is an update to
hopefully put us on the same page again.
First, a review of the repos available, since this is always a point
of confusion:
http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora
- This is Juan's tree from
Akio Takebe wrote: [Thu Jul 27 2006, 04:46:45AM EDT]
BZ's patch is old.
Today 139 cset is added to linux-2.6-xen-fedora tree.
So I think we should use Aron's patches.
Thanks, I just put an updated patch in BZ 199684, but best approach is
to work from the mercurial trees I described in my
Akio,
I intentionally omitted this from what I submitted to Juan because the
rpm currently backs out ALL the xen modifications to the tpm code.
But you're right... to build from linux-2.6-xen-fedora-ia64, you need
to either (1) apply this patch, or (2) disable tpm in the config.
Aron
Akio
Hi Keir,
We finally seem to have mostly stabilized with the latest big changes
in xen-unstable.hg. Therefore, please pull:
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
Changeset 10831 of this tree is in sync with cset 10756 of
xen-unstable.hg. Highlights include:
* credit
On Thu, 2006-07-27 at 16:15 +0800, Zhang, Xiantao wrote:
This patch intends to remove the confusing flag ARCH_VMX_CONTIG_MEM for
VTi. It was used for indicating that VTi needs contiguous memory.
Currently, it seems useless. In addition, add the flag ARCH_VMX_DOMAIN
to ensure VMX_DOMAIN check
On Thu, 2006-07-27 at 11:03 +0200, Tristan Gingold wrote:
Hi,
this is the first patch for drivers domains. With this patch and another one
for pcifront, I was able to use an ethernet card in a domU.
Very cool! Applied.
--
Alex Williamson HP Open Source
On Thu, 2006-07-27 at 14:35 +0200, Tristan Gingold wrote:
Hi,
this patch allows IO ports to be mapped/unmapped in domU.
Using it I was able to mount a usb-key in domU.
Applied.
--
Alex Williamson HP Open Source Linux Org.
On Thu, 2006-07-27 at 16:36 +0200, Tristan Gingold wrote:
Hi,
debug message to be removed.
Applied.
--
Alex Williamson HP Open Source Linux Org.
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
If you are trying to run a specific app that runs
on 32bit Red Hat Linux (without porting or recompiling),
you may be able to run it using ia32el (the Intel IA-32
Execution Layer**) on a Red Hat ia64 guest OS running
on xen-ia64. However as others have pointed out,
xen-ia64 doesn't support
Hello,
I know that Xen is now setup for IA-64 but how setup is it. I noticed that
many bugs are out there, are these minor errors or is IA-64 still
problematic? I guess I really want to know how close Xen is to being fully
optimized on IA-64?
On Thu, 2006-07-27 at 15:18 -0700, David Drummond wrote:
Hello,
I know that Xen is now setup for IA-64 but how setup is it. I noticed that
many bugs are out there, are these minor errors or is IA-64 still
problematic? I guess I really want to know how close Xen is to being fully
Hi Isaku,
Thank you for investigating the VTI booting issues. In my side, this issue is a
little hard to reproduce. Actually we only see a few times in the past 2 weeks.
Do you often meet this situation?
For the credit schedule, we are preparing to switch schedule from bvt to credit
in our
On Fri, Jul 28, 2006 at 08:55:36AM +0800, You, Yongkang wrote:
Hi Isaku,
Thank you for investigating the VTI booting issues. In my side, this issue is
a little hard to reproduce. Actually we only see a few times in the past 2
weeks. Do you often meet this situation?
Hi Yongkan.
Always it
Hi Alex,
I remembered I have sent out the patch to increase
CONFIG_NR_CPUS to 16 for domain0 to enable SMP. It works well on Tiger4
platform but you said it would break HP's box. Seems need to think more
about this issue before change:)
Thanks Best Regards
-Xiantao
OTC,Intel Corporation
-Original Message-
From: Isaku Yamahata [mailto:[EMAIL PROTECTED]
Sent: 2006年7月28日 9:39
To: You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report
-Cset#10811:254c090854de
little hard to reproduce. Actually we only see a few times in
On Fri, 2006-07-28 at 09:42 +0800, Zhang, Xiantao wrote:
Hi Alex,
I remembered I have sent out the patch to increase
CONFIG_NR_CPUS to 16 for domain0 to enable SMP. It works well on Tiger4
platform but you said it would break HP's box. Seems need to think more
about this issue before
Xen/IA64 Healthiness Report
Good news: VTI domain can start up in new Qemu 0.8.1 without vif option.
Bad news: __coexisting__ domain testing failed in latest upstream. That means
can not create 2 domains at the same time.
Testing Environment:
Platform: Tiger4
From: Isaku Yamahata
1. SMP_VTI_Boot may stop to boot after Calibrating delay loop...
I'm seeing a similar issue.
My case is UP VTI domain. VTI domain doesn't share pcpu with dom0.
FWIW
- vITV
By inserting debug print code to vtm_set_itv(), vtm_set_itm() and
vtm_timer_fn(), I found that
Hi Tristan, Isaku,
Thanks for your reply and sorry for my ignorance...
I tried recompile with CONFIG_NR_CPUS=8.
As it turned out, I can boot up with 4 CPUs when specifying
dom0_max_vcpus=4.
[EMAIL PROTECTED] ~]# xm vcpu-l
Name ID VCPU CPU State Time(s) CPU
BTW, two XenU domain coexisting testing can pass in Changeset 10818:199d53efd029
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年7月28日 10:49
To: xen-ia64-devel@lists.xensource.com
Subject:
Akio Takebe wrote: [Thu Jul 27 2006, 09:00:41PM EDT]
To know what hypervisor changeset to use, check the spec file:
cd kernel-cvs-ia64/devel
grep -m1 xen_hv_cset kernel-2.6.spec
Which is this cset xen-ustable's cset or xen-ia64-unstable's cset?
xen-unstable
Aron
Zhang, Xiantao wrote: [Thu Jul 27 2006, 09:13:23PM EDT]
Thanks you for detail. Seems very clear now. I have the same
question with Akio. Which Cset for xen and xenLinux is using for
debug? Are they compatible?
I have a tracker on my web page that might help answer this question.
It updates
Yes. Xm list shows everything is right. But I can not connect to the 2nd one.
Could you? :(
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Alex Williamson [mailto:[EMAIL PROTECTED]
Sent: 2006年7月28日 11:11
To: You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com
Subject: RE:
48 matches
Mail list logo
