similar to: [XEN][vNUMA][PATCH 9/9] Disable Migration with numa_strategy

Enables numa if vnuma topology hypercall is supported and it is domU. Signed-off-by: Elena Ufimtseva <ufimtseva@gmail.com> --- arch/x86/xen/setup.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c index 68c054f..0aab799 100644 --- a/arch/x86/xen/setup.c +++ b/arch/x86/xen/setup.c @@ -20,6 +20,7 @@ #include

Defines XENMEM subop hypercall for PV vNUMA enabled guests and data structures that provide vNUMA topology information from per-domain vnuma topology build info. Signed-off-by: Elena Ufimtseva <ufimtseva@gmail.com> --- Changes since RFC v2: - fixed code style; - the memory copying in hypercall happens in one go for arrays; - fixed error codes logic; --- xen/common/domain.c | 10

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1320922479 0 # Node ID bc79b560aafa1e4dc42af00e6a326dc651b5636a # Parent 460b507e15f864dd6712f5040e36538d6e076ae4 libxl: use named options for tsc_mode. It seems that this knob is expoerted from the hypervisor as a raw integer (no symbolic names) documented in xen/include/asm-x86. Propagating that all the way to the

On Sun, Jun 28, 2020 at 02:34:37PM +0800, Jason Wang wrote: > > On 2020/6/25 ??9:57, Stefan Hajnoczi wrote: > > These patches are not ready to be merged because I was unable to measure a > > performance improvement. I'm publishing them so they are archived in case > > someone picks up this work again in the future. > > > > The goal of these patches is to

On Sun, Jun 28, 2020 at 02:34:37PM +0800, Jason Wang wrote: > > On 2020/6/25 ??9:57, Stefan Hajnoczi wrote: > > These patches are not ready to be merged because I was unable to measure a > > performance improvement. I'm publishing them so they are archived in case > > someone picks up this work again in the future. > > > > The goal of these patches is to

These patches are not ready to be merged because I was unable to measure a performance improvement. I'm publishing them so they are archived in case someone picks up this work again in the future. The goal of these patches is to allocate virtqueues and driver state from the device's NUMA node for optimal memory access latency. Only guests with a vNUMA topology and virtio devices spread

These patches are not ready to be merged because I was unable to measure a performance improvement. I'm publishing them so they are archived in case someone picks up this work again in the future. The goal of these patches is to allocate virtqueues and driver state from the device's NUMA node for optimal memory access latency. Only guests with a vNUMA topology and virtio devices spread

After syncing to the latest xen-unstable sources, I am getting following compilation error : make[3]: *** No rule to make target `/data/xen-sources/xen-unstable.hg/stubdom/ioemu/i386-stubdom/qemu.a'', needed by `/data/xen-sources/xen-unstable.hg/stubdom/mini-os-x86_32-ioemu/mini-os_app.o''. Stop. make[3]: Leaving directory

libxl__domain_build_info_setdefault may be called several times, so rtc_timeoffset can''t be setted in it. Move rtc_timeoffset setting logic to libxl__build_pre. Reported-by: Teck Choon Giam <giamteckchoon@gmail.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Lin Ming <mlin@ss.pku.edu.cn> --- tools/libxl/libxl_create.c | 9 ---------

I have been following Dulloor''s patch series for NUMA. The last patch set was submitted in Aug 2010 (titled NUMA v2). I''m interested in testing / experimenting with his NUMA changes but cannot find them in http://xenbits.xensource.com/xen-unstable.hg. Is there some way I can download or clone the Xen branch where Dulloor''s patches have been applied? Thanks. Dante

Hmmm... It appears I never posted the corrected version of this patch so it never made it upstream. See: http://lists.xen.org/archives/html/xen-devel/2011-11/msg00587.html http://lists.xen.org/archives/html/xen-devel/2011-11/msg02145.html It would be good if this very minor fix was also applied to 4.2 (and, if possible, 4.1). Thanks, Dan =================== The program xen-tmem-list-parse

Hi all, this is a non comprehensive list of missing features in libxenlight and\or xl: - xen_platform_pci flag support in VM config files; - relative paths support in VM config files; - hap support in VM config files; - -c option to xl create; - remus; - trigger command; - tmem-* commands; - sched-* commands; - usb-* commands; - scsi-* commands. In general if you execute "xm

I see that "xl list" shows a domain waiting idly for console input as "r", whereas "xm list" shows the same domain as "b". I also see that the State field for "xl list" contains only three characters (e.g. "r--"), whereas "xm list" shows six (e.g. "-b----"). Is this expected/intended (e.g. "r" in xm list

A while ago (I think at the Xummit), I recall someone saying that the structure of the files in xenlinux may change soon so that the xen-specific files would move to a subdirectory or arch/<arch> (e.g. linux/arch/i386/xen instead of linux/arch/xen/i386). Is this still planned? If so, what is the timing? If it''s in progress, I''d like to get in the loop... Thanks, Dan

Hello everyone! With the completion of our first few release candidates for 4.2, it''s time to look forward and start planning for the 4.3 release. I''ve volunteered to step up and help coordinate the release for this cycle. The 4.2 release cycle this time has been nearly a year and a half. One of the problems with having such a long release is that people who get in features

This patch series implements the hypervisor portion of transcendent memory as described at http://oss.oracle.com/projects/tmem Tools patches to follow. All patches are sent as attachments as my mailer tends to mess with attached text. Apologies to those for whom this is inconvenient. Signed-off-by: Dan Magenheimer <dan.magenheimer.com> [1] Public interface for tmem [2] add pointer to

Implement "rtc_timeoffset" and "localtime" options compatible as xm. rtc_timeoffset is the offset between host time and guest time. localtime means to specify whether the emulted RTC appears as UTC or is offset by the host. Acked-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Lin Ming <mlin@ss.pku.edu.cn> --- docs/man/xl.cfg.pod.5 | 8 ++++++++

Various versions of Linux under various circumstances select TSC as the primary clocksource for the kernel. This is especially true for uniprocessor kernels, but also in some cases for multiprocessor kernels. In most cases, this is because a processor bit (tsc_invariant? constant_tsc?) is passed through directly from the hardware via Xen and tested by the hvm guest and the result implies that

FYI, it is likely that ocfs2 will not work on 3.7-rcN until the following one-line patch is merged, as the code in ramster that provoked it is directly leveraged from ocfs2 o2net. > From: Tejun Heo [mailto:tj at kernel.org] > Sent: Thursday, October 18, 2012 5:39 PM > To: Dan Magenheimer > Cc: linux-kernel at vger.kernel.org; Konrad Wilk > Subject: [PATCH] workqueue:

Folks, The second release candidate for Xen 3.4.0 is available at http://xenbits.xensource.com/xen-unstable.hg, tagged as ''3.4.0-rc2''. Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel