similar to: RE: [PATCH]Check the values of MAX_VIRT_CPUS and NR_CPUSfor SMP

Displaying 20 results from an estimated 2000 matches similar to: "RE: [PATCH]Check the values of MAX_VIRT_CPUS and NR_CPUSfor SMP"

2006 Apr 21
1
RE: [PATCH]Check the values of MAX_VIRT_CPUS and NR_CPUSfor SMP
>From: Tristan Gingold [mailto:Tristan.Gingold@bull.net] >Sent: 2006年4月21日 15:26 >> > >> >See how we solve this on x86 near the top of do_boot_cpu() in >> >arch/x86/smpboot.c. Essentially we allocate extra idle domains on >> >demand to give us enough idle vcpus for one per physical cpu. >> > >> > -- Keir >> >> Yes,
2006 Apr 21
1
RE: [PATCH]Check the values of MAX_VIRT_CPUS and NR_CPUSfor SMP
>From: Keir Fraser >Sent: 2006年4月21日 14:41 > > >On 21 Apr 2006, at 02:31, Atsushi SAKAI wrote: > >> But the logical limit of the IA64 Max CPU is larger than 64. >> If someone change these values, some possibility make this error >again. >> >> To avoid this problem, I believe this check code should be exists. > >See how we solve this on x86 near
2006 May 23
0
RE: [Xen-ia64-devel] Re: PATCH: split smpboot.c and createcpuhotplug.c
>From: Tristan Gingold >Sent: 2006年5月23日 15:30 > >Le Lundi 22 Mai 2006 17:44, Keir Fraser a écrit : >> On 22 May 2006, at 08:57, Tristan Gingold wrote: >> > this patch creates a new file: cpuhotplug.c. The content is the >xenbus >> > handler part of smpboot.c. The purpose is to be able to share this >> > part with >> > other architectures.
2006 Jan 26
2
do_* declarations (was: Re: [Xen-ia64-devel] [PATCH] added multicall)
Hi, on ia64, the do_* functions for hypercalls are called in C. However, they are not declared in any .h file. I think it is cleaner to declare them in an header file rather than locally. The question is in which header file. Thank you for any suggestion. The do_* functions are at least: extern long do_ni_hypercall(void); extern long do_dom0_op(dom0_op_t *u_dom0_op); extern long
2010 Apr 06
3
[LLVMdev] Idea for Google Summer Code : C Compiler for EFI Byte Code implement in LLVM
On Apr 6, 2010, at 1:10 AM, Tristan Gingold wrote: > > On Apr 3, 2010, at 2:36 PM, Russell Wallace wrote: > >> On Fri, Apr 2, 2010 at 6:17 PM, Chris Lattner <clattner at apple.com> wrote: >>> No, please don't. This is something we specifically do not want to support. The issue is not the parser, the issue is that struct field offsets are no longer constant in
2008 Jun 19
0
[PATCH] ia64/xen: introduce definitions necessary for ia64/xen hypercalls.
import include/asm-ia64/xen/interface.h to introduce introduce definitions necessary for ia64/xen hypercalls. They are basic structures to communicate with xen hypervisor and will be used later. Cc: Robin Holt <holt at sgi.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at
2008 Jun 19
0
[PATCH] ia64/xen: introduce definitions necessary for ia64/xen hypercalls.
import include/asm-ia64/xen/interface.h to introduce introduce definitions necessary for ia64/xen hypercalls. They are basic structures to communicate with xen hypervisor and will be used later. Cc: Robin Holt <holt at sgi.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at
2006 Aug 21
7
RFC: xencomm in common
Hi, xencomm is the ppc infrastructure to do hypercalls with guest physical addresses instead of virtual address. Because ia64 should also use physicall address, I think it''s better to re-use the ppc code and to put into common code. I''d propose to submit this patch is every part is OK (ie no NAK). This patch creates include/xen/xencomm_access.h which is to be included by
2006 Oct 18
0
[PATCH][ACM] 1/3: make acm_setup arch independent
Please pick up Tristan Gingold''s patch referenced below. The 2nd and 3rd parts build on top of it. http://lists.xensource.com/archives/html/xen-devel/2006-09/msg00120.html Stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 Aug 17
5
Re: [XenPPC] Xencomm for xen/ia64
(CCed to xen-devel for completeness. ;) On Wed, 2006-08-16 at 17:24 +0200, Tristan Gingold wrote: > I am porting xen-ppc''s xencomm to xen/ia64. > Currently on xen/ia64 copy_from/to_guest uses guest virtual address. This > works well as long as the virtual addresses are in the TLB. When not in TLB > (or vTLB) the hypercall can''t success without domain help. The
2005 May 02
0
[PATCH] update evtchn for SMP
# This is a BitKeeper generated diff -Nru style patch. # # ChangeSet # 2005/05/01 17:01:17-07:00 kmacy@curly.lab.netapp.com # add SMP support to evtchn # Signed-off-by: Kip Macy <kmacy@netapp.com> # # freebsd-5.3-xen-sparse/i386-xen/include/xen_intr.h # 2005/05/01 17:01:15-07:00 kmacy@curly.lab.netapp.com +3 -0 # add SMP interfaces # #
2006 Aug 23
3
PATCH: xencomm - kernel side
Hi, taking into account Hollis comments I now submit this patch. IA64 specific stuff will be posted to xen-ia64-unstable after merge. Tristan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 Aug 02
0
Regressions with BVT
Hi everyone, I understand BVT is not the default scheduler anymore, but perhaps this would be of interest to some people. Some changes in the current BVT scheduler compared to the BVT code in Xen 3.0 has affected its correctness. In the original (Xen 3.0) BVT scheduler the weights resulted in correct CPU allocations. However, the current BVT scheduler (CS 10647:8e55c5c11475) does not do it
2006 Apr 21
4
[Xen-ia64-devel] flush_tlb_mask and grant_table on ia64
Hi, on IA64 flushing the whole TLB is very expensive: this is a cpu tlb flush and clearing 16MB of memory (virtual tlb). However, flushing an address range is rather cheap. Flushing an address range on every processors is also cheap (no IPI). Unfortunatly Xen common code flushes the whole TLB after unmapping grant reference. Currently, this is not done on IA64 because domain_dirty_cpumask
2006 Apr 27
1
BVT scheduling with command line
Hello I''m in trouble using the bvt scheduler with the command line. the command "xm sched-bvt help" explain that it need 6 argument but that''s all. I have read a previous conversation for bvt example with command line, but it doesn''t work I try (5 is the id of the concerned
2007 Jun 23
2
PATCH: add xc_domain_setdebugging in xenctrl API
Hi, for ia64, I''d like to add xc_domain_setdebugging() in the xenctrl API. This patch implements it and modifies xc_ptrace.c to use it. The rationnal is enabling debugging tool not based on the ptrace API. The ptrace API is based on Linux ptrace which (at least on ia64) doesn''t have many privilegied registers. I''d prefer this patch being integrated on
2006 Jun 14
0
bvt scheduler parameters confusion!
hi all, im am trying to allocate cpu to the various domains using a bvt scheduler. so now lets say i want to give the first virtual machine a weight of 1 and the second a weight of 2. this should result in domain1 using 33% of the cpu and domain2 66%. however since xm sched-bvt takes inverse of the weights as input so i do 1/1 and 1/2 and hence do "xm sched-bvt vm1 2 0 0 0 0" for the
2006 Aug 03
3
RE: [Patch][RFC] Support "xm dump" (is Re: Re: [Patch]Enable "sysrq c" handler for domU coredump)
Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as
2006 Dec 04
1
[PATCH] buildconfigsfor pvfb
I have a similar patch for this, which is generated in linux-2.6.16.33-xen/.config automatically. See attachment defbuild.patch. Pae_new_config is used to build x86_32 with PAE enabled. Ping >-----Original Message----- >From: xen-ia64-devel-bounces@lists.xensource.com [mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Atsushi >SAKAI >Sent: 2006年12月4日 12:22 >To:
2005 May 17
8
scheduler independent forced vcpu selection
I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler