Hi,
This patch removes warning message in fw_emul.c.
Tested by booting Domain-0 and running the efibootmgr on
Domain-0.
Signed-off-by: Masaki Kanno [EMAIL PROTECTED]
Best regards,
Kan
remove_warning.patch
Description: Binary data
___
In some scenarios, xen_timer_interrupt will not set machine itm,
this may make this LP not receive timer interrupt any more.
Signed-off-by: Anthony Xu [EMAIL PROTECTED]
Thanks,
Anthony
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Xu, Anthony
Sent:
Hi, Anthony
Could you explain following cases?
Anyway, thank you for your patch of pal_halt_light domU.
Thanks,
Atsushi SAKAI
In some scenarios, xen_timer_interrupt will not set machine itm,
this may make this LP not receive timer interrupt any more.
Signed-off-by: Anthony Xu [EMAIL
Assume dom0(UP) and VTI-domain(UP) are running on a same LP,
1. dom0 sets itm, assume machine itm is set to this itm.
2. dom0 is scheduled out to other LP,
3. VTI-domain is scheduled in.
4. VTI-domain is blocked due to emulating hal_light.
5. idle_dom is schedule in.
6. machine timer interrupt
Hi Yongkang,
Hi all,
I find a strange issue that if I only assign 1 or 2 vcpus to dom0, I can
not use vcpu-pin to pin the No. 0 vcpu. It will report: Invalid argument.
But it works, if I let Xen0 see all vcpus when booting.
For example, in IA32, set (dom0-cpus 1)
After Xen0 boot up, xm vcpu-p
On 28/8/06 10:34 am, Masaki Kanno [EMAIL PROTECTED] wrote:
Hi Keir,
Do you have good ideas to solve this problem?
Yes, but not before 3.0.3. We need to add code to the tail of the scheduler
to migrate the previously running VCPU to a different runqueue.
-- Keir
Hi Kan,
I have tried your patch with 2 vcpus assigned to Xen0. It can work with several
times retry. When failed times, it just reported: device or resource busy.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Masaki Kanno [mailto:[EMAIL PROTECTED]
Sent: 2006年8月28日
Hi Yongkang,
Hi all,
I find a strange issue that if I only assign 1 or 2 vcpus to dom0, I can
not use vcpu-pin to pin the No. 0 vcpu. It will report: Invalid argument.
But it works, if I let Xen0 see all vcpus when booting.
For example, in IA32, set (dom0-cpus 1)
After Xen0 boot up, xm
Alex Williamson wrote:
On Mon, 2006-08-28 at 08:35 +0900, [EMAIL PROTECTED] wrote:
In PV-on-HVM driver code, is_running_on_xen and HYPERVISOR_ioremap
have to be used as valid feature. Thus we modified like this.
Doesn't the below do what you need w/o breaking the CONFIG_XEN=n
build?
Hi,
this patch puts hypercalls, acpi and EFI tables on 3 separated 4KB pages. So
dom_fw should now work even if page size is 4KB.
I have added comments and made other small changes. I really hope dom_fw.c is
now easy to understand.
Tested by running dom0 and domU.
Tristan.
# HG changeset
All 3 ia64 patches from this thread are now applied. Thanks,
Alex
--
Alex Williamson HP Open Source Linux Org.
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
On Mon, 2006-08-28 at 15:21 +0900, Masaki Kanno wrote:
Hi,
This patch removes warning message in fw_emul.c.
Applied.
--
Alex Williamson HP Open Source Linux Org.
___
Xen-ia64-devel mailing list
On Mon, 2006-08-28 at 14:32 +0800, Xu, Anthony wrote:
In some scenarios, xen_timer_interrupt will not set machine itm,
this may make this LP not receive timer interrupt any more.
Applied, thanks for debugging this one Anthony!
Alex
--
Alex Williamson HP
On Mon, 2006-08-28 at 09:56 +0200, Tristan Gingold wrote:
Hi,
small patch to fix some warnings.
Applied.
--
Alex Williamson HP Open Source Linux Org.
___
Xen-ia64-devel mailing list
On Mon, 2006-08-28 at 22:03 +0900, Akio Takebe wrote:
Hi,
I make a patch to print command line of Xen when Xen boot.
I'd like to submit it for xen-3.0.3.
Applied.
--
Alex Williamson HP Open Source Linux Org.
___
On Mon, 2006-08-28 at 22:44 +0900, Akio Takebe wrote:
Hi,
I fix machine_hlt to support noreboot option.
I'd like to submit it for xen-3.0.3.
Applied. I used the cpu_halt() from the existing linux-xen file
instead of recreating it in domain.c. Thanks,
Alex
--
Alex Williamson
On Mon, 2006-08-28 at 16:41 +0200, Tristan Gingold wrote:
Hi,
this patch puts hypercalls, acpi and EFI tables on 3 separated 4KB pages. So
dom_fw should now work even if page size is 4KB.
Applied.
--
Alex Williamson HP Open Source Linux Org.
On Mon, 2006-08-28 at 13:59 +0200, Tristan Gingold wrote:
Hi,
this patch implements xencomm for xen/ia64.
I post it for comments and evaluation. I'd like to know wether or not it
fixes the domain creation failure bug (it seems so, but please confirm).
I thought to submit it after 3.0.3
Alex Williamson wrote: [Fri Aug 25 2006, 10:38:50AM EDT]
On Fri, 2006-08-25 at 08:57 -0400, Aron Griffis wrote:
Would anybody mind if I create a bugzilla.xensource.com account for
the xen-ia64-devel ML? The goal is that the ML could be cc'd on ia64
bugs, to prevent a split of effort.
Xen/IA64 Healthiness Report
11320 has some improvements in VTI and XenU stability.
In nightly testing, it only catches can not allocate memory issue twice.
VTI unstable issue has been fixed by Anthony.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2
Hi Tsunehisa,
Sorry for very late response,
I noticed that you use do_yield instead of do_block in xen-event.patch.
I think do_yield will incur some unnecessary schedule before it can resume to
Guest.
And if there are only VTI-domain and IDLE-domain running on one LP,
VTI-domain calling
21 matches
Mail list logo
