search for: armbru

...y want to extend it to cover semantic aspects, CLI, and experimental features. If you want to learn more, check out the last three commit messages in the series. = Patches = [PATCH v2 00/30] Configurable policy for handling deprecated interfaces Message-Id: <20200303163505.32041-1-armbru@redhat.com> https://lists.nongnu.org/archive/html/qemu-devel/2020-03/msg00645.html = Git = Tag patchew/20200303163505.32041-1-armbru@redhat.com in repository https://github.com/patchew-project/qemu.git

These patches address issues in the kernel part of xenoprof: * Ill-advised use of on_each_cpu() can lead to sleep with interrupts disabled. * Race conditions in active_domains code. * Cleanup of active_domains code. Comments welcome. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

On Wed, Mar 04, 2020 at 03:48:34PM +0100, Markus Armbruster wrote: > I understand libguestfs comes with integration tests. You might be > interested in something I'm developing for QEMU 5.0 to permit "testing > the future". I'd like to ensure it is actually useful before I > continue. Let me know what you think. > &g...

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1306311631 -3600 # Node ID 6b1fe0cba8a2f0bcc1274c8e777da5b6c198b45d # Parent 8258c5a0ba35de937597e2c516bc88f8ebe1be35 libxl: use preferred syntax for network device creation with upstream qemu Markus Armbruster points out in <m3r582pzc1.fsf@blackfin.pond.sub.org> on qemu-devel that this is the prefered syntax going forward. Using it avoid needlessly instantiating a qemu "vlan" and instead creates a simply host end point and device. Signed-off-by: Ian Campbell <ian.campbell@citrix.c...

Peter Maydell <peter.maydell@linaro.org> writes: > On Mon, 14 Sep 2020 at 09:55, Markus Armbruster <armbru@redhat.com> wrote: >> >> New option -compat lets you configure what to do when deprecated >> interfaces get used. This is intended for testing users of the >> management interfaces. It is experimental. >> >> -compat deprecated-input=<in-pol...

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

...ys/hypervisor/uuid, containing this domain''s UUID. Stripping off /vm/ from the value of vm to get the UUID isn''t exactly nice. The alternative is to add a XENVER_get_uuid code to HYPERVISOR_xen_version(), but I''m not sure that''s worth it. Signed-off-by: Markus Armbruster <armbru@redhat.com> diff -r ddba92a5cba9 drivers/xen/core/xen_sysfs.c --- a/drivers/xen/core/xen_sysfs.c Tue May 09 12:41:38 2006 +0200 +++ b/drivers/xen/core/xen_sysfs.c Thu May 18 18:06:35 2006 +0200 @@ -8,12 +8,14 @@ */ #include <linux/config.h> +#include <linux/err.h&g...

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

...tty registers, we can't yet know whether the PVFB is enabled. By the time we can know (xenstore is up), the console setup game is over. Enable the Xen console hvc by default, and make it the preferred console. Change the preferred to tty when PVFB probes successfully. Signed-off-by: Markus Armbruster <armbru at redhat.com> --- This patch supersedes the "xen: Make hvc0 the preferred console in domU" patch. It does not depend on the PVFB patch; it works with and without it. Aside: xenfb_make_preferred_console() may not be the best way to solve the problem. I simply followed...

...tty registers, we can't yet know whether the PVFB is enabled. By the time we can know (xenstore is up), the console setup game is over. Enable the Xen console hvc by default, and make it the preferred console. Change the preferred to tty when PVFB probes successfully. Signed-off-by: Markus Armbruster <armbru at redhat.com> --- This patch supersedes the "xen: Make hvc0 the preferred console in domU" patch. It does not depend on the PVFB patch; it works with and without it. Aside: xenfb_make_preferred_console() may not be the best way to solve the problem. I simply followed...

...tty registers, we can't yet know whether the PVFB is enabled. By the time we can know (xenstore is up), the console setup game is over. Enable the Xen console hvc by default, and make it the preferred console. Change the preferred to tty when PVFB probes successfully. Signed-off-by: Markus Armbruster <armbru at redhat.com> --- This patch supersedes the "xen: Make hvc0 the preferred console in domU" patch. It does not depend on the PVFB patch; it works with and without it. Aside: xenfb_make_preferred_console() may not be the best way to solve the problem. I simply followed...