Re: [Xen-devel] patch about "don't reset vcpu_info on a cancelled suspend"
On 2016/1/4 19:54, David Vrabel wrote: > On 29/12/15 05:49, Ouyangzhaowei (Charles) wrote: >> Hi David, >> >> This patch has been applied to for-linus-4.1b, and we wonder if this patch >> will be applied to linux kernel, or does >> it still needs more test to apply to linux kernel? > > Sorry, it looks like I forgot to send a pull request for this patch. > I'd applied it to for-linus-4.5 and tagged it for stable. OK, thanks! > > David > > . > ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
[Xen-devel] patch about "don't reset vcpu_info on a cancelled suspend"
Hi David, This patch has been applied to for-linus-4.1b, and we wonder if this patch will be applied to linux kernel, or does it still needs more test to apply to linux kernel? thanks On 2015.5.28 19:07, David Vrabel wrote: >> vcpu_info would be reset to wrong place on canceled suspend on PVOPS VM >> which has multi-cpu >> >> The hypervisor continues assuming that vcpu_info is stored in per-cpu data >> which was set up by xen_vcpu_setup(), >> while on canceled suspend, the call to xen_hvm_init_shared_info() will make >> the guest think that vcpu_info >> is in the shared page. This will cause non-boot cpus keep checking a wrong >> vcpu_info address and can not handle >> irqs any more after suspend canceled, for example after we do "xl save >> -c/restore", PVOPS VM can not be resumed >> as the cpus can not finish their irqs. >> >> >> Signed-off-by: Charles Ouyang >> Reviewed-by: Boris Ostrovsky >> Reviewed-by: David Vrabel > > 1. I don't think I offered a reviewed-by tag for this patch > 2. You did not Cc the xen-devel mailing list on this patch. > 3. The patch is white-space damaged. > 4. The commit message has lines longer than ~72 chars. > > But I've applied this to for-linus-4.1b anyway, thanks. > > David ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] Redhat 6 VM crash on Xen when cpu number reaches 64
Hi all: Now a days, we tested Redhat 6.2(6.4) on Xen(version 4.1.2). If we config the cpu number more than 32, it'll show 32 in the VM, and if we config it 64 cpus, the VM will crash and the log is list below. Can someone tell us why is this happening? Old RHEL6 kernels don't have support for VCPU info placement for PVHVM (VCPUOP_register_vcpu_info call) so only 32 VCPUs are supported. This is fixed in current 6.6.z kernel. Hi Vitaly, Is there any official announcement of this on Redhat website? We did not find any explanation about this, can you help us to find it? thanks very much thanks ===crash log= CPU: CPU feature rdtscp disabled on xen guest CPU: CPU feature constant_tsc disabled on xen guest mce: CPU supports 0 MCE banks #32 CPU32: Stuck ?? #33 CPU33: Stuck ?? ... -- Vitaly ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
