similar to: [PATCH] Fix compilation on ARM

The commit 874f76a "PL011: fix reverse logic for interrupt mask register" introduced regression on the Versatile Express. The board didn''t receive correctly input. The timeout interrupt may be asserted when the FIFO is not empty, and no futher data is received over a 32-bit period. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- xen/drivers/char/pl011.c | 2

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

Host S3 implicitly resets the host TSC to 0, but the tsc offset for hvm domains is not recalculated when they resume, causing it to go into negative values. In Linux guest using tsc clocksource, this results in a hang after wrap back to positive values since the tsc clocksource implementation expects it reset. Signed-off-by: Tomasz Wroblewski <tomasz.wroblewski@citrix.com> ---

Since OMAP UART has a few distinct features than common 8250 UART, I re-implemented its driver rather than porting it based on ns16550.c. There are mainly two big differences between the implementations. First, OMAP UART introduces the concept of register access mode, which divides the register map into seperated space. Switching the access mode is then necessary when configuring it. Second, THRE

Widen SERHND_IDX (and use it where needed), introduce a flush low level driver method, and remove unnecessary peeking of the common code at the (driver specific) serial port identification string in the "console=" command line option value. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/smpboot.c +++ b/xen/arch/x86/smpboot.c @@ -1017,7 +1017,7 @@ void __init

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. As before several of the patches are not to be applied because they can be done better using infrastructure from Julien''s "Allow Xen to boot with a raw Device Tree" patch. They are included for completeness. With

FYI, I see the following build error with this patch... MRJ ---- new warnings/errors for xen ---- keyhandler.c: In function `__dump_execstate'': keyhandler.c:96: warning: asm operand 1 probably doesn''t match constraints gmake[5]: *** [keyhandler.o] Error 1 gmake[4]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/common/built_in.o] Error 2 gmake[3]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/xen]

[CCing the libguestfs mailing list - as Rich responded on IRC about your question on timeout.] On Sun, Feb 21, 2016 at 10:07 PM, Thomas Kee <xsited@yahoo.com> wrote: > Hi Kashyap, > > Thanks for offering to help. The day job caused a pause and it took me an > hour to reassert where I was in the process. I usually hang out on freenet > as xsited. I am still reading the

Prior to c/s 23811:f1349a968a5a LSR_THRE was checked only once, while there it got promoted into the surrounding loop''s condition. Since that bit may not clear for an extended period of time (i.e. when no new output is generated), it must not be used in this way indefinitely. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/char/ns16550.c +++

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. With this rebase I''ve picked up some patches from Julien which were required to do things properly, so the gic v7 and device blacklisting patches have been changed to use the proper mechanisms. Previously I was able to boot

Hi, I'm trying to use libvirt for an armel virtual machine hosted into an x86_64 box. I know the command line to start qemu-system-arm directly, but I cannot figure a proper .xml configuration file to let libvirt do this job. The main problem is that I want a serial console attached via telnet, this is the Qemu incantation: -serial telnet::4000,server,nowait,nodelay Wahtever I do in

On Mon, Feb 17, 2014 at 05:01:05PM +0100, Niccolo Rigacci wrote: > Hi, > > I'm trying to use libvirt for an armel virtual machine hosted > into an x86_64 box. > > I know the command line to start qemu-system-arm directly, but I > cannot figure a proper .xml configuration file to let libvirt do > this job. > We're still missing a full support for qemu-system-arm

On Tue, Feb 18, 2014 at 09:33:01AM +0100, Martin Kletzander wrote: > > > > > Wahtever I do in libvirt, I get this paramter added: > > > > > > -device isa-serial > > > > > > > and this is new-style for x86 qemu, however, arm-based qemu haven't > > adopted this option yet. > > > > To be a bit more precise, only *some*

On x86 ioremap() is not suitable here, set_fixmap() must be used instead. Also replace some literal numbers by their proper symbolic constants, making the code easier to understand. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/char/ns16550.c +++ b/xen/drivers/char/ns16550.c @@ -20,6 +20,9 @@ #include <xen/pci.h> #include <xen/pci_regs.h> #include

On Tue, Feb 18, 2014 at 09:10:58AM +0100, Martin Kletzander wrote: > On Mon, Feb 17, 2014 at 05:01:05PM +0100, Niccolo Rigacci wrote: > > Hi, > > > > I'm trying to use libvirt for an armel virtual machine hosted > > into an x86_64 box. > > > > I know the command line to start qemu-system-arm directly, but I > > cannot figure a proper .xml

On 02/18/2014 04:03 AM, Niccolo Rigacci wrote: > On Tue, Feb 18, 2014 at 09:33:01AM +0100, Martin Kletzander wrote: >>> >>>> Wahtever I do in libvirt, I get this paramter added: >>>> >>>> -device isa-serial >>>> >>> >>> and this is new-style for x86 qemu, however, arm-based qemu haven't >>> adopted this

On Mon, 2020-01-06 at 20:31 +0100, daggs wrote: > > > I'm using ubuntu 16.04 with libvirt 1.3.1, if this is a version issue, I can upgrade to latest version. > > > what I'm I missing? > > > > Your version of libvirt (as well as QEMU and virt-manager, I assume) > > is fairly old, and aarch64 support specifically has seen quite a few > >

Hi, I want to try Xen on ARMv8 Simulator. Can you please provide guidance?. I am looking for information about sources, build and procedure to launch Xen on ARMv8 Thanks & Regards Vijay

On Sun, Oct 9, 2016 at 7:25 AM, Oliver Mangold via Syslinux <syslinux at zytor.com> wrote: > Hi, > > I would like to point out an issue with the enumeration of ISA serial > devices in Syslinux. If I interpret the snippet below correctly, Syslinux > looks up the device order with the BIOS, while Linux uses the fixed order > 3F8,2F8,3E8,2E8. > > Note that this

Hi, I would like to point out an issue with the enumeration of ISA serial devices in Syslinux. If I interpret the snippet below correctly, Syslinux looks up the device order with the BIOS, while Linux uses the fixed order 3F8,2F8,3E8,2E8. Note that this inconsistency is a real problem, as some motherboards (like e.g. a Supermicro X10DRi with default BIOS settings) have a different order