Public bug reported:
What happened:
I ran the 9front installation ISO (here:
http://r-36.net/9front/9front-3853.02ebd469f43a.iso.bz2) in QEMU, with a blank
qcow2, using `qemu-system-i386 -hda 9front.qcow2.img -cdrom
9front-3853.02ebd469f43a.iso -boot d -vga std -m 1G`. During the console boot,
From: Alex Friedman
According to the specification, the low 16 bits should contain the number of
I/O submission queues, and the high 16 bits should contain the number of
I/O completion queues.
Signed-off-by: Alex Friedman
---
hw/block/nvme.c | 6 --
1 file changed, 4 insertions(+), 2
Public bug reported:
QEMU version: 2.4, also tested b37686f (2015-10-09 12:18:13 +0100) not working.
Requires KVM and SDL, possibly others.
Kernel version: 4.1 working, 4.2 not working.
Architecture: x86_64
Target: x86_64, also tested i386 not working.
Step 0: Install versions listed above.
Step
what we were testing.
Anyway I'll keep an eye on this and if I get hardware capable of
testing it, then I'll do so.
Rich.
/--Regards, Alex/
On 15/01/16 19:07, Richard W.M. Jones wrote:
On Thu, Jan 14, 2016 at 05:35:21PM +0100, Laszlo Ersek wrote:
On 01/14/16 11:23, Richard W.M. Jones wrote:
On Thu, Jan 14, 2016 at 01:06:05PM +0300, Alex wrote:
Richard, I just posted HW test results to
https://bugzilla.redhat.com/show_bug.cgi?id
Public bug reported:
Execution line:
qemu-system-i386.exe -m 512 c:\Disks\Qemu_XP_en.vhd -serial pipe:windbg
It waits for the pipe.
Execute windbg
c:\WINDDK\7600.16385.1\Debuggers\windbg.exe -k
com:pipe,port=\\.\pipe\windbg,resets=0,reconnect
GUI black screen shown. QEMU hangs.
qemu v1.5.3 (c
It seems the same problem with windbg #1225187
The patch above does not solve the problem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1181796
Title:
Qemu locks up when incoming serial fills up
Preferred Domain Availability Notice:
planet-ltc.com will be listed for auction in a few days. This domain might be
useful for you, since you own a domain similar to this domain.
To confirm interest in owning this domain, fill out the simple form here:
planet-ltc.com
Sincerely,Alex
Preferred Domain Availability Notice:
planet-ltc.com will be listed for auction in a few days. This domain might be
useful for you, since you own a domain similar to this domain.
To confirm interest in owning this domain, fill out the simple form here:
planet-ltc.com
Sincerely,Alex
Preferred Domain Availability Notice:
planet-ltc.com will be listed for auction in a few days. This domain might be
useful for you, since you own a domain similar to this domain.
To confirm interest in owning this domain, fill out the simple form here:
planet-ltc.com
Sincerely
Preferred Domain Availability Notice:
planet-ltc.com will be listed for auction in a few days. This domain might be
useful for you, since you own a domain similar to this domain.
To confirm interest in owning this domain, fill out the simple form here:
planet-ltc.com
Sincerely
fixed in linux
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1505062
Title:
Regression: QEMU 2.4 on Linux 4.2 fails to init display with SMM
ena
It is well docummented. The defalt nic card is ne2k-pci and it is not Debian
specific.
--
Alex.
"Geert Stappers" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> ___
> Qemu-devel mailing list
> Qem
This patch has been around for a while but never committed to the
mainstream.
Are there any known issues with the patch?
--
Alex.
"Julian Seward" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Could somebody please commit, or at least consider committin
I have not updated my sources this week. But in the past few months I had to
manually apply the patch to make Qemu workable. And I use it a lot. Thanks
for a great product.
--
Alex.
"Julian Seward" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Saturday
ter that I was able to login to netware network with
"net use" but the Novel login crushed if I had not been already
authenticated. It looks like NT4 guest do have similar problems, but XP does
not.
Needless to say that both NT and 2k client work fine on real
ter that I was able to login to netware network with
"net use" but the Novel login crushed if I had not been already
authenticated. It looks like NT4 guest do have similar problems, but XP does
not.
Needless to say that both NT and 2k client work fine on real
vl.o(.text+0x57b0): In function `do_savevm':
c:/qemu/vl.c:4570: undefined reference to `gettimeofday'
--
Alex.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
of QEMU with no problem (last time from
from a July 27 snapshot)
--
Alex.
"Armistead, Jason" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Alex
>
> Some inevitable question others will ask:
>
> what is your machine's configuration and bu
Thanks all,
I updated my CVS tree this morning and it compiled fine.
Obviously, the problem has been fixed already fixed.
Alex.
"WaxDragon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> > Use this patch.
> > http://lists.gnu.org/archive/html/qemu
after install had been complete.
When I attach the debugger, I always get the similar result (below).
Does this make sense to you?
Thank you,
Alex.
(gdb) where
#0 0x77f813b2 in ntdll!DbgUiConnectToDbg () from
C:\WINNT\system32\NTDLL.DLL
#1 0x7c57fe8f in KERNEL32!DebugActiveProcess ()
f
Brad Campbell wrote:
> Brad Campbell wrote:
>> G'day all,
>>
>> I've had *great* results running win2k and xp with -kernel-kqemu on an
>> Athlon host under linux 2.6,
>> however my experiments using a linux guest have resulted in complete
>> kernel bombs..
>> Is there anything I should be doing/t
Are you sure coreect spelling is "qmeu-disk", not "qemu-disk"?
--
Alex.
"Yann Le Doaré" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
my option is "-hda /mnt/partitions/windows0/qmeu-disk"
Le dimanche 07 mai 2006 à 05:44 -0300, Andr
(0);
+}
}
static void sdl_show_cursor(void)
{
if (!kbd_mouse_is_absolute()) {
- SDL_SetCursor(sdl_cursor_normal);
+ SDL_ShowCursor(1);
}
}
--
Alex.
"Johannes Schindelin" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
It is well docummented. The defalt nic card is ne2k-pci and it is not Debian
specific.
Alex.
- Original Message -
From: "Geert Stappers" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.emulators.qemu
Sent: Friday, June 16, 2006 11:17 PM
Subject: Re: linux-test-0.5.1.tar.g
vl.o(.text+0x57b0): In function `do_savevm':
c:/qemu/vl.c:4570: undefined reference to `gettimeofday'
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
vl.o(.text+0x57b0): In function `do_savevm':
c:/qemu/vl.c:4570: undefined reference to `gettimeofday'
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Hi,
The patch below allows me to compile qemu on Windows, however it is still
not working.
The program exits immediately reporting that it can't open the hard disk
image.
GDB reports the offensive pies of code is in malloc(), which does not make
sense to me.
Am I doing something wrong?
qemu_malloc
That's better. What's wrong with QCOW?
--
Alex.
"Kazu" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> alex wrote:
>
>> Hi,
>> The patch below allows me to compile qemu on Windows, however it is still
>> not working.
>> Th
;Kazu" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Alex wrote:
>
> > That's better. What's wrong with QCOW?
> >
>
> Qcow uses aio interface but aio emulation is not fully implemented.
>
> Regards,
> Kazu
_
--- /d/qemu/block-raw.c Mon Oct 2 13:55:48 2006
+++ block-raw.c Mon Oct 2 13:42:55 2006
@@ -1134,6 +1134,10 @@
{
}
+void qemu_aio_flush(void)
+{
+}
+
void qemu_aio_wait_start(void)
{
}
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://
This is a second attempt to post, first one did not get through.
This patch fixes -parallel and -serial options work with TCP targets on
Windows host.
Alex.
--- /d/qemu/vl.c Fri Jan 12 10:43:12 2007
+++ vl.c Fri Jan 12 10:49:37 2007
@@ -2692,8 +2692,13 @@
if (ret <
This works for me:
eject cdrom
switch back to windows and try to access the cdrom. Now windows will
complain that there is no media in the drive.
switch to qemu console
change cdrom /whatever
go back to windows and try again. This time Window should see the correct
media.
--
Alex.
"De
Public bug reported:
I use qemu-i386 with IntelHaxm on Windows 10 x64 host with Windows 7 x86 guest.
I run the guest till OS loads and create a snapshot with savevm, then close
qemu, run it again and try to load the snapshot with loadvm. The guest crashes
or freezes. I dumped registers on snaps
Dear Qemu Genius
This is zaifeng (wzf_develo...@foxmail.com) (WeChat ID: QemuKVM).
Yes, I am a cloud engineer. (๑•̀ㅂ•́)و✧
May I ask you some questions about Qemu?
Here is the problem:
If you use IDE disk on a Windows VM, "QEMU HARDDISK" could be found from devi
Public bug reported:
I am using LVM VGs on MD-raid1 for hosting my KVM volumes. On the host,
a VG looks like this:
Disk /dev/vm/vol202a: 60 GiB, 64424509440 bytes, 125829120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/opti
Public bug reported:
steps to reproduce:
1. run a Wayland compositor (I use sway, probably the same bug exists for other
compositors)
2. execute qemu -display gtk,gl=on
expected results:
a GTK window is created that shows SeaBIOS failing to boot
actual results:
segmentation fault qemu-syste
** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1855617
Title:
savevm with hax saves wrong register state
Status in QEMU:
New
Bug description:
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1775011
Title:
-display gtk,gl=on crashes on Wayland
Status in QEMU:
Fix Released
Bug
Hello,
I have the same qemu behaviour. It happens every time I have unplugged physical
usb device attached to guest from the host system. My device is USB GSM dongle.
Some times it disconnects and reconnects again for unknown reason, may be power
loss... With version 3.1.0 qemu (gentoo linux) th
Issues with time emulation. MacOS runs on qemu with a specific cpu option: -cpu
Penryn,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on.
The code of cpu_x86_cpuid has no handler for 0x4010, so vmware-cpuid-freq
is ignored.
Another solution is to modify tsc_increment_by_tick value in
MSR_IA32
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1829242
Title:
qemu on windows host exits after savevm command
Status in QEMU:
Fix
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1829242
Title:
qemu on windows host exits after savevm command
Status in QEMU:
Fix Committed
Hi,
No, no messages, no crash window which appears when windows catches unhandled
exceptions in software. Looks as if there was an asynchronous command to exit
during savevm which executed in parallel to the command.
--
You received this bug notification because you are a member of qemu-
devel-
To do this I must crosscompile qemu on a linux host and debug on a
windows host. Is there a gdb for 64-bit windows, since windows debuggers
don't understand DWARF debugging info, and is it possible to give him
paths to source files, since paths on the build machine and the
debugging machine will be
Running the operation under debugger catches this error:
Critical error detected c374
(2314.a54): Break instruction exception - code 8003 (first chance)
ntdll!RtlIsNonEmptyDirectoryReparsePointAllowed+0x72:
7ffe`0780b2d2 cc int 3
This error means that a heap corruption
I'm still unable to see all locals, but can output some of them with
printf. qemu_savevm_state_iterate is called 35 times, iterates over
timer, COLOState, slirp, block and ram entrys, and the error is on
handling ram entry.
--
You received this bug notification because you are a member of qemu-
d
Public bug reported:
I'm running qemu-system-i386.exe 3.1.0 with this command line:
"C:\Program Files\qemu\qemu-system-i386.exe" -L C:\user\qemu\pc-bios\ -name
win7 -m 4G -uuid 564db62e-e031-b5cf-5f34-a75f8cefa98e -rtc base=localtime
-accel hax -hdd C:\VirtualMachines\Dev\Win10x64_VS17\swap.qco
On Mon, 2012-08-06 at 15:40 +, Bhushan Bharat-R65777 wrote:
> Hi Avi/All,
>
> I am facing issue to boot KVM guest on x86 (I used to work on PowerPC
> platform and do not have enough knowledge of x86). I am working on making
> VFIO working on PowerPC Booke, So I have cloned A
On Thu, 2012-08-09 at 17:39 +, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: Stuart Yoder [mailto:b08...@gmail.com]
> > Sent: Thursday, August 09, 2012 8:28 PM
> > To: Bhushan Bharat-R65777
> > Cc: Alex Williamson; qemu-devel@nongn
On Thu, 2012-08-09 at 18:06 +, Bhushan Bharat-R65777 wrote:
>
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Thursday, August 09, 2012 11:25 PM
> > To: Bhushan Bharat-R65777
> > Cc: Stuart Yoder;
On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
> Alex Williamson writes:
>
> > VFIO kernel support was just merged into Linux, so I'd like to
> > formally propose inclusion of the QEMU vfio-pci driver for
> > QEMU 1.2. Included here is support for x86 P
On Mon, 2012-08-13 at 17:48 +0200, Andreas Hartmann wrote:
> Alex Williamson wrote:
> > On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
> >> Alex Williamson writes:
> >>
> >>> VFIO kernel support was just merged into Linux, so I'd like to
On Mon, 2012-08-13 at 18:36 +0200, Andreas Hartmann wrote:
> Alex Williamson schrieb:
> > On Mon, 2012-08-13 at 17:48 +0200, Andreas Hartmann wrote:
> >> Alex Williamson wrote:
> >>> On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
> >>>>
On Mon, 2012-08-13 at 14:33 -0500, Anthony Liguori wrote:
> Alex Williamson writes:
>
> > On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
> >> Alex Williamson writes:
> >>
> >> > VFIO kernel support was just merged into Linux, so I'd l
On Mon, 2012-08-13 at 20:48 +, Blue Swirl wrote:
> On Mon, Aug 13, 2012 at 7:33 PM, Anthony Liguori wrote:
> > Alex Williamson writes:
> >
> >> On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
> >>> Alex Williamson writes:
> >>>
On Mon, 2012-08-13 at 17:18 -0500, Anthony Liguori wrote:
> Alex Williamson writes:
> > +static int vfio_load_rom(VFIODevice *vdev)
> > +{
> > +uint64_t size = vdev->rom_size;
> > +const VMStateDescription *vmsd;
> > +char name[32];
> > +
On Mon, 2012-08-13 at 17:19 -0500, Anthony Liguori wrote:
> Jan Kiszka writes:
>
> > On 2012-08-01 07:18, Alex Williamson wrote:
> >> Signed-off-by: Alex Williamson
> >> ---
> >>
> >> MAINTAINERS |5 +
> >>
On Tue, 2012-08-14 at 08:12 +0100, Stefan Hajnoczi wrote:
> On Tue, Jul 31, 2012 at 11:18:15PM -0600, Alex Williamson wrote:
> > This adds the core of the QEMU VFIO-based PCI device assignment driver.
> > To make use of this driver, enable CONFIG_VFIO, CONFIG_VFIO_IOMMU
On Tue, 2012-08-14 at 18:53 +0300, Avi Kivity wrote:
> On 08/01/2012 08:18 AM, Alex Williamson wrote:
> > This adds the core of the QEMU VFIO-based PCI device assignment driver.
> > To make use of this driver, enable CONFIG_VFIO, CONFIG_VFIO_IOMMU_TYPE1,
> > and CONFIG_VFIO_P
> On 2012-08-02 21:17, Alex Williamson wrote:
> > +
> > +static int vfio_msix_vector_use(PCIDevice *pdev,
> > +unsigned int vector, MSIMessage msg)
> > +{
> > +VFIODevice *vdev = DO_UPCAST(VFIODevice, pdev, pdev);
> > +
.2-v2
tags/vfio-pci-for-qemu-1.2-v3
Blue Swirl already offered an Ack-by for previous version, I'll
hope, but won't assume that carries forward. Original description
below with updated tag. Thanks,
Alex
VFIO kernel support was just merged into Linux, so I'd like to
formal
Signed-off-by: Alex Williamson
---
scripts/update-linux-headers.sh |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
index 9d2a4bc..270d32b 100755
--- a/scripts/update-linux-headers.sh
+++ b/scripts/update
Signed-off-by: Alex Williamson
---
MAINTAINERS |5 +
configure |6 ++
hw/i386/Makefile.objs |1 +
3 files changed, 12 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 708ad54..327b219 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -468,6
Based on Linux as of ddf343f6. Note that vfio.h isn't yet an
installed header at this commit, but is fixed by trivial update to
include/linux/Kbuild.
Signed-off-by: Alex Williamson
---
linux-headers/asm-s390/kvm.h |2
linux-headers/asm-s390/kvm_para.h |2
linux-headers/as
ed a reviewed-by for this version and Blue Swirl offered an
acked-by for prior versions. If we don't have sufficient sign-offs by
the deadline it'll have to wait for 1.3. Thanks,
Alex
(void)
{
__asm__ volatile ("int $8");
}
$ gcc test.c
$ ./a.out
Segmentation fault
$
... and not a kernel panic (double fault)
Forgive me for sending this patch as attachment, I'm not used to git.
Best Regards,
Alex
x86 software emulation (non-KVM mode) does not check privi
(void)
{
__asm__ volatile ("int $8");
}
$ gcc test.c
$ ./a.out
Segmentation fault
$
... and not a kernel panic (double fault)
Best Regards,
Alex
---
x86 software emulation (non-KVM mode) does not check privilege
levels on task gate switches ... so one can invoke a kernel&
On Sat, 2012-08-18 at 00:28 +1000, Alexey Kardashevskiy wrote:
> On Fri, Jun 22, 2012 at 6:16 PM, Alexey Kardashevskiy wrote:
>
> > On 07/06/12 09:17, Alex Williamson wrote:
> > > On Fri, 2012-05-25 at 17:35 +1000, Alexey Kardashevskiy wrote:
> > >> Some adapters
On Mon, 2012-08-20 at 10:55 +0200, Jan Kiszka wrote:
> No need to expose the fd-based interface, everyone will already be fine
> with the more handy EventNotifier variant. Rename the latter to clarify
> that we are still talking about irqfds here.
>
> Signed-off-by: Jan Kiszka
Ping, no response so far ...
Thanks,
Alex
Alex ZUEPKE wrote:
> Hi,
>
> x86 software emulation (non-KVM mode) does not check privilege levels on
> task gate switches ... so one can invoke a kernel's double fault handler
> from user space -- very bad.
>
> Expected beha
On Tue, 2012-08-28 at 09:23 +, Bhushan Bharat-R65777 wrote:
> Hi Alex,
>
> In my susyem I have following devices:
>
> I tried assigning a following PCI devices:
> 00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI
> Controller (rev 03)
> 00:0
t on these, I'll
split up and post the VFIO PCI bus driver for inclusion as well.
I can also host the above vfio-next branch for inclusion in
linux-next. Please review and comment. Thanks,
Alex
v2: Interrupt setup ioctl rework based on comments by Konrad.
The interrupt ioctls are no lon
Including rationale for design, example usage and API description.
Signed-off-by: Alex Williamson
---
Documentation/vfio.txt | 359
1 files changed, 359 insertions(+), 0 deletions(-)
create mode 100644 Documentation/vfio.txt
diff --git a
This defines both the user and bus driver APIs.
Signed-off-by: Alex Williamson
---
Documentation/ioctl/ioctl-number.txt |1
include/linux/vfio.h | 395 ++
2 files changed, 396 insertions(+), 0 deletions(-)
create mode 100644 include/linux
This provides the base group management with conduits to the
IOMMU driver and VFIO bus drivers.
Signed-off-by: Alex Williamson
---
drivers/vfio/vfio_main.c| 1248 +++
drivers/vfio/vfio_private.h | 36 +
2 files changed, 1284 insertions(+), 0
Enable the base code.
Signed-off-by: Alex Williamson
---
MAINTAINERS |8
drivers/Kconfig |2 ++
drivers/Makefile |1 +
drivers/vfio/Kconfig |8
drivers/vfio/Makefile |3 +++
5 files changed, 22 insertions(+), 0 deletions(-)
create
Backing for operations on the IOMMU object, including DMA
mapping and unmapping.
Signed-off-by: Alex Williamson
---
drivers/vfio/vfio_iommu.c | 611 +
1 files changed, 611 insertions(+), 0 deletions(-)
create mode 100644 drivers/vfio/vfio_iommu.c
&proxy->msix_bar, 1, 0)) {
> -pci_register_bar(&proxy->pci_dev, 1, PCI_BASE_ADDRESS_SPACE_MEMORY,
> +pci_register_bar(&proxy->pci_dev, 1, PCI_BASE_ADDRESS_SPACE_MEMORY |
> + PCI_BASE_ADDRESS_MEM_TYPE_64,
> &proxy->msix_bar);
> } else
> vdev->nvectors = 0;
>
I was also able to add MEM64 BARs to device assignment pretty trivially
and it seems to work, guest sees 64bit BARs for an 82576 VF, programs it
to an fexx address and it works.
Alex
On Wed, 2012-01-25 at 14:13 +1100, David Gibson wrote:
> On Tue, Dec 20, 2011 at 09:30:37PM -0700, Alex Williamson wrote:
> > On Wed, 2011-12-21 at 14:32 +1100, David Gibson wrote:
> > > On Mon, Dec 19, 2011 at 04:41:56PM +0100, Joerg Roedel wrote:
> > > > On Mon, De
I was trying to add signalfd support on qemu-ppc (specifically, I'm
doing a configure with "--enable-debug-tcg --enable-debug
--disable-strip --disable-kvm --disable-bsd-user --disable-darwin-user
--enable-profiler --target-list=ppc-linux-user --disable-curl
--enable-nptl").
At first I thought tha
I have read that one of the reasons for using makecontext is that it
saves the signal state. But there also exist functions like
"sigsetjmp" and "siglongjmp" which can be used to jump around the
coroutines while preserving signal masks.
I have a patch that uses sigsetjmp and siglongjmp instead of
On Fri, Jan 27, 2012 at 15:39, Paolo Bonzini wrote:
>> I have a patch that uses sigsetjmp and siglongjmp instead of
>> makecontext and getcontext (and all the ucontext stuff), and it
>> *seems* to work... but I'm not sure if it works "by accident" (not
>> sure what I'm doing to the stack, not sure
On Wed, 2012-02-01 at 15:46 +1100, David Gibson wrote:
> This patch adds code to the code for the powernv platform to create
> and populate isolation groups on hardware using the p5ioc2 PCI host
> bridge used on some IBM POWER systems.
>
> Signed-off-by: Alexey Kardashevskiy
> Signed-off-by: Davi
On Wed, 2012-02-01 at 11:58 -0700, Alex Williamson wrote:
> On Wed, 2012-02-01 at 15:46 +1100, David Gibson wrote:
> > This patch adds code to the code for the powernv platform to create
> > and populate isolation groups on hardware using the p5ioc2 PCI host
> > bridge u
v_phb_type {
> @@ -60,6 +62,10 @@ struct pnv_ioda_pe {
>
> /* Link in list of PE#s */
> struct list_headlink;
> +
> +#ifdef CONFIG_DEVICE_ISOLATION
> + struct device_isolation_group di_group;
> +#endif
Embedding the struct means we need to know the size, which means we
can't get rid of the #ifdef. Probably better to use a pointer if we
don't mind adding a few bytes in the #ifndef case. Thanks,
Alex
> };
>
> struct pnv_phb {
to a group to something like vfio binding to that group and
creating a chardev to access it? Are we manipulating automatic driver
binding or existing bound drivers once a group is bound? Do isolation
groups enforce isolation, or just describe it? Thanks,
Alex
As we start to enable 64bit I/O devices, there's a good chance
we'll find bugs and compatibility issues. This allows a user
to toggle off (default on) 64bit PCI MMIO BARs, downgrading
them to 32bit BARs.
Signed-off-by: Alex Williamson
---
Should this be an "x-mem64" optio
On Thu, 2012-02-02 at 01:14 +0200, Michael S. Tsirkin wrote:
> On Wed, Feb 01, 2012 at 03:57:02PM -0700, Alex Williamson wrote:
> > As we start to enable 64bit I/O devices, there's a good chance
> > we'll find bugs and compatibility issues. This allows a user
> > t
On Wed, 2012-02-01 at 15:57 -0700, Alex Williamson wrote:
> As we start to enable 64bit I/O devices, there's a good chance
> we'll find bugs and compatibility issues. This allows a user
> to toggle off (default on) 64bit PCI MMIO BARs, downgrading
> them to 32bit BARs.
&g
I am barely able to understand this inline function:
static inline int sas_ss_flags(unsigned long sp)
{
return (target_sigaltstack_used.ss_size == 0 ? SS_DISABLE
: on_sig_stack(sp) ? SS_ONSTACK : 0);
}
(signal.c @97)
... and it seems wrong to me when used in the following function
On Tue, Feb 7, 2012 at 12:18, Stefan Hajnoczi wrote:
> On Sat, Jan 28, 2012 at 9:31 AM, Alex Barcelo wrote:
>> On Fri, Jan 27, 2012 at 15:39, Paolo Bonzini wrote:
>>>> I have a patch that uses sigsetjmp and siglongjmp instead of
>>>> makecontext and getcontext
Signed-off-by: Alex Barcelo
---
linux-user/signal.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/linux-user/signal.c b/linux-user/signal.c
index 79a39dc..26e0530 100644
--- a/linux-user/signal.c
+++ b/linux-user/signal.c
@@ -4115,7 +4115,7 @@ static target_ulong
On Sun, Feb 5, 2012 at 00:00, Peter Maydell wrote:
> On 4 February 2012 14:26, Alex Barcelo wrote:
>> (...)
> This looks like a bug, yes -- the other architectures have the !
> (or equivalent code) in their get_sigframe() implementations so
> probably ppc is just wrong here.
Ye
On Thu, Feb 9, 2012 at 19:43, Andreas Färber wrote:
> Am 09.02.2012 19:30, schrieb Alex Barcelo:
>> Signed-off-by: Alex Barcelo
>
> This patch needs a better description than "bug",
sorry, something like "Incorrect zero comparison in sas_ss_flags"
would have
done wrong only for this
architecture, it's more a typo than a bug). It's NOT ppc specific,
it's POSIX standard (sigaltstack) and qemu internal.
I have a test source that I will send in a follow-up (it's longer than
I would have wished, I'm sure that a better test case can be
// Test source and desired /real output:
#include
#include
#include
#include
void handler(int sig)
{
unsigned int a;
// to prevent uninitialized stack, normally a = 0
if ( a>10 ) a = 0;
a = a + 1;
printf ("new value: %d\n" , a );
if (a > 7) _exit(a);
return;
}
int main()
I have sent a v2 of this patch (renaming it, with a description and a
test case). If it's not trivial and I have to send it in another way,
I will do so.
Sorry for the inconvenience, as I said I'm new here and maybe I
misunderstood the "trivial" category.
(file pth_mctx.c, variant 2).
It's my first patch, I'm sure that there are things that I
have done wrong. Please, be kind :)
Thanks for your time
Alex Barcelo (3):
coroutine: adding sigaltstack method (.c source)
coroutine: adding control flags (enable/disable) for ucontext
c
This file is based in both coroutine-ucontext.c and
pth_mctx.c (from the GNU Portable Threads library).
The mechanism used to change stacks is the sigaltstack
function (variant 2 of the pth library).
Signed-off-by: Alex Barcelo
---
coroutine-sigaltstack.c | 337
1 - 100 of 26486 matches
Mail list logo
