search for: habkost

This series contain fixes to make the paravirt_ops code compile and boot on x86_64. This is a follow-up for the previous series from Glauber.

This series contain fixes to make the paravirt_ops code compile and boot on x86_64. This is a follow-up for the previous series from Glauber.

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does not ign...

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does not ign...

...gnored, and is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrmsr(0x410, 0xfffffffffffffbff) during MCE initialization) --- arch/x86...

...gnored, and is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrmsr(0x410, 0xfffffffffffffbff) during MCE initialization) --- arch/x86...

...1468] - [net] virtio_net: mergeable receive buffers (Mark McLoughlin ) [473120] - [net] virtio_net: jumbo frame support (Mark McLoughlin ) [473114] - [xen] virtio_net: some relatively minor fixes (Mark McLoughlin ) [468034] - [xen] virtio: include headers in kernel-headers package (Eduardo Pereira Habkost ) [446214] - [xen] virtio: add PV network and block drivers for KVM (Mark McLoughlin ) [446214] ************************* Do you think if i am safe to keep using the virtio drivers within the same kernel ? Thanks Jatin

On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > the {rd,wr}msr instructions. This makes serious issues (either on the > guest kernel, or on the host) be silently ignored, and is different from > the native MSR code (which does not ignore the exceptions)....

...o_net: mergeable receive buffers (Mark McLoughlin ) [473120] > - [net] virtio_net: jumbo frame support (Mark McLoughlin ) [473114] > - [xen] virtio_net: some relatively minor fixes (Mark McLoughlin ) [468034] > - [xen] virtio: include headers in kernel-headers package (Eduardo > Pereira Habkost ) [446214] > - [xen] virtio: add PV network and block drivers for KVM (Mark > McLoughlin ) [446214] > ************************* > > Do you think if i am safe to keep using the virtio drivers within the > same kernel ? > > Thanks > Jatin So they are comfortable not main...

Hi All My guest is a CentOS 5.4 VM: [root at localhost ~]# uname -a Linux localhost 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux [root at localhost ~]# cat /etc/*release CentOS release 5.4 (Final) I wanted to know if the virtio drivers on this guest are stable. The reason for asking this question is that i found this link:

....com> Doug Goldstein <cardoe@cardoe.com> Dunrong Huang <huangdr@cloud-times.com> Dunrong Huang <riegamaths@gmail.com> Ed Maste <emaste@freebsd.org> Edgar E. Iglesias <edgar.iglesias@gmail.com> Edgar E. Iglesias <edgar.iglesias@xilinx.com> Eduardo Habkost <ehabkost@redhat.com> Eduardo Otubo <otubo@linux.vnet.ibm.com> Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Ekaterina Tumanova <tumanova@linux.vnet.ibm.com> Eric Blake <eblake@redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.fl...

....com> Doug Goldstein <cardoe@cardoe.com> Dunrong Huang <huangdr@cloud-times.com> Dunrong Huang <riegamaths@gmail.com> Ed Maste <emaste@freebsd.org> Edgar E. Iglesias <edgar.iglesias@gmail.com> Edgar E. Iglesias <edgar.iglesias@xilinx.com> Eduardo Habkost <ehabkost@redhat.com> Eduardo Otubo <otubo@linux.vnet.ibm.com> Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Ekaterina Tumanova <tumanova@linux.vnet.ibm.com> Eric Blake <eblake@redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.fl...

....com> Doug Goldstein <cardoe@cardoe.com> Dunrong Huang <huangdr@cloud-times.com> Dunrong Huang <riegamaths@gmail.com> Ed Maste <emaste@freebsd.org> Edgar E. Iglesias <edgar.iglesias@gmail.com> Edgar E. Iglesias <edgar.iglesias@xilinx.com> Eduardo Habkost <ehabkost@redhat.com> Eduardo Otubo <otubo@linux.vnet.ibm.com> Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Ekaterina Tumanova <tumanova@linux.vnet.ibm.com> Eric Blake <eblake@redhat.com> Eric Johnson <ericj@mips.com> Erlon Cruz <erlon.cruz@br.fl...

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have

Currently we have an OCaml library for generating the qemu command line (used only by ‘virt-v2v -o qemu’). However we also generate a qemu command line in ‘lib/launch-direct.c’, and we might in future need to generate a ‘-readconfig’-compatible configuration file if we want to go beyond 10,000 drives for scalability testing. Therefore this patch series reimplements the qemu command line code as

This should help us to: - More easily add or remove machine initialization arguments without having to change every single machine init function; - More easily make mechanical changes involving the machine init functions in the future; - Let machine initialization forward the init arguments to other functions more easily. This change was half-mechanical process: first the struct was added