Am 05.01.2011 07:42, Huang Ying wrote:
On Tue, 2011-01-04 at 16:32 +0800, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
There is no need to restrict writing back MCE MSRs to reset or full
state updates as setting their values has no side effects.
Sorry for late.
Don't worry.
Am 05.01.2011 07:45, Huang Ying wrote:
On Fri, 2010-12-31 at 17:10 +0800, Jan Kiszka wrote:
Am 31.12.2010 06:22, Huang Ying wrote:
In Linux kernel HWPoison processing implementation, the virtual
address in processes mapping the error physical memory page is marked
as HWPoison. So that, the
Am 05.01.2011 um 00:56 schrieb Aurelien Jarno:
On Tue, Jan 04, 2011 at 11:53:01PM +0100, Andreas Färber wrote:
Am 04.01.2011 um 21:07 schrieb Aurelien Jarno:
On Tue, Jan 04, 2011 at 08:54:04PM +0100, Andreas Färber wrote:
Am 03.01.2011 um 15:34 schrieb Aurelien Jarno:
We don't have any
On Tue, Jan 04, 2011, Alexander Graf wrote about Re: [Qemu-devel] [PATCH] Add
VMX cpuid feature to qemu64:
If qemu-kvm still uses the qemu64 type, that's plainly a bug :). It really
should use -cpu kvm64 / kvm32 as default.
When I run qemu-kvm's qemu-system-x86_64, and look at the CPU I get
On 01/05/2011 10:17 AM, Nadav Har'El wrote:
On Tue, Jan 04, 2011, Alexander Graf wrote about Re: [Qemu-devel] [PATCH] Add VMX
cpuid feature to qemu64:
If qemu-kvm still uses the qemu64 type, that's plainly a bug :). It really
should use -cpu kvm64 / kvm32 as default.
When I run qemu-kvm's
On Wed, 2011-01-05 at 16:07 +0800, Jan Kiszka wrote:
Am 05.01.2011 07:42, Huang Ying wrote:
On Tue, 2011-01-04 at 16:32 +0800, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
There is no need to restrict writing back MCE MSRs to reset or full
state updates as setting their
On Wed, Jan 05, 2011, Avi Kivity wrote about Re: [Qemu-devel] [PATCH] Add VMX
cpuid feature to qemu64:
The intent of kvm64/qemu64 is to provide some feature stability, so that
when you run a guest with those cpu types, you get something expected.
So adding to them isn't a good idea.
I
On 01/04/2011 05:43 PM, Anthony Liguori wrote:
The fact that the iothread drops the global lock during sleep is a
detail that shouldn't affect correctness. The IO thread is
absolutely allowed to run for arbitrary periods of time without
dropping the qemu mutex.
No, it's not, since it will
On 01/05/2011 10:50 AM, Nadav Har'El wrote:
On Wed, Jan 05, 2011, Avi Kivity wrote about Re: [Qemu-devel] [PATCH] Add VMX cpuid
feature to qemu64:
The intent of kvm64/qemu64 is to provide some feature stability, so that
when you run a guest with those cpu types, you get something expected.
Am 05.01.2011 09:33, Huang Ying wrote:
On Wed, 2011-01-05 at 16:07 +0800, Jan Kiszka wrote:
Am 05.01.2011 07:42, Huang Ying wrote:
On Tue, 2011-01-04 at 16:32 +0800, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
There is no need to restrict writing back MCE MSRs to reset or full
On 12/21/2010 05:05 AM, Wen Congyang wrote:
When I use the command 'virsh save' to save the domain state,
I receive the following error message:
operation failed: Migration unexpectedly failed.
I debug the qemu by adding some printf(), and find the function
pclose() returns -1.
I use strace to
On Wed, Jan 05, 2011, Avi Kivity wrote about Re: [Qemu-devel] [PATCH] Add VMX
cpuid feature to qemu64:
IMO the emphasis on defaults is misplaced. Most people run virtual
machines via a management tool, and we should focus on making it easy
for management tool maintainers to do the right
On Tue, Jan 04, 2011 at 12:37:37PM -0700, Alex Williamson wrote:
rtl8139 includes a cpu_register_io_memory() in it's vmstate. This
is problematic if the guest undergoes hotplug operations, which can
shift io indexes between migration source and target. Add an
interface to detect this
On Wed, Jan 05, 2011 at 09:15:43AM +0100, Andreas Färber wrote:
Am 05.01.2011 um 00:56 schrieb Aurelien Jarno:
On Tue, Jan 04, 2011 at 11:53:01PM +0100, Andreas Färber wrote:
Am 04.01.2011 um 21:07 schrieb Aurelien Jarno:
On Tue, Jan 04, 2011 at 08:54:04PM +0100, Andreas Färber wrote:
Am
From: Jes Sorensen jes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
architectures. Otherwise qemu-img will fail to create disk
images = 2GB
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
cutils.c |8
monitor.c |2 +-
qemu-common.h
On Tue, Jan 04, 2011 at 02:43:11PM -0500, Mike Frysinger wrote:
i've been working on a new architecture port, but i cant quite figure
out some of the intricacies from reading the code. i have all the
simple stuff working for linux-user (register moves, immediate moves,
loads, stores, syscall
On 1 January 2011 18:25, Aurelien Jarno aurel...@aurel32.net wrote:
SMMLA and SMMLS are broken on both in normal and thumb mode, that is
both (different) implementations are wrong. They try to avoid a 64-bit
add for the rounding, which is not trivial if you want to support both
SMMLA and SMMLS
Must be fixed in arch/x86/include/asm/kvm_emulate.h and
arch/x86/kvm/emulate.c.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/688085
LinkedIn
Alexandre Felipe Muller de Souza requested to add you as a
connection on LinkedIn:
--
Jiajun,
Eu gostaria de adicioná-lo à minha rede profissional no LinkedIn.
-Alexandre
Accept invitation from Alexandre Felipe Muller de Souza
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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/688085
Title:
Guest kernel hang during boot when KVM is active on i386
On Wed, Dec 08, 2010 at 03:08:59PM -0200, Marcelo Tosatti wrote:
Use _RMV method to indicate whether device can be removed.
Data is retrieved from QEMU via I/O port 0xae0c.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Acked-by: Gleb Natapov g...@redhat.com
Index:
Can you later post your patch or link to this bug? Then I can help
testing it with rootstock.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/604872
Title:
qemu-system-arm segfaults emulating
Change proposal for Maverick (2.6.35) based on kernel patch in description:
* kvm_emulate.h:
* Change struct operand so that val and orig_val will be changed from
unsigned long to union like this:
union {
unsigned long val;
u64 val64;
On Tuesday 04 January 2011 15:00:12 Alexander Graf wrote:
I have this very issue with s390. The only host to run (and compile)
this on is an s390. And few people have those. So it breaks from time to
time.
I have some pages bookmarked hinting how to get S390 Linux to boot under
From: Jan Kiszka jan.kis...@siemens.com
This is required to support keeping VCPU states across a system reset.
If we do not read the current state before the reset,
cpu_synchronize_all_post_reset may write back incorrect state
information.
The first user of this will be MCE MSR synchronization
From: Jan Kiszka jan.kis...@siemens.com
Reorder mcg_status in CPUState to achive automatic clearing on reset.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/cpu.h|3 ++-
target-i386/helper.c |2 --
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git
From: Jan Kiszka jan.kis...@siemens.com
If the kernel does not support KVM_CAP_ASYNC_PF, it also does not know
about the related MSR. So skip it during state synchronization in that
case. Fixes annoying kernel warnings.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |
On 05.01.2011, at 13:07, Rob Landley wrote:
On Tuesday 04 January 2011 15:00:12 Alexander Graf wrote:
I have this very issue with s390. The only host to run (and compile)
this on is an s390. And few people have those. So it breaks from time to
time.
I have some pages bookmarked hinting
On Wed, Jan 05, 2011 at 11:41:02AM +0100, jes.soren...@redhat.com wrote:
From: Jes Sorensen jes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
architectures. Otherwise qemu-img will fail to create disk
images = 2GB
Signed-off-by: Jes Sorensen
On 01/05/11 13:34, Michael S. Tsirkin wrote:
On Wed, Jan 05, 2011 at 11:41:02AM +0100, jes.soren...@redhat.com wrote:
From: Jes Sorensen jes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
architectures. Otherwise qemu-img will fail to create disk
images = 2GB
On Mon, Jan 03, 2011 at 03:34:33PM +0100, Aurelien Jarno wrote:
Implement the correct NaN propagation rules for ARM targets by
providing an appropriate pickNaN function.
Also fix the #ifdef tests for default NaN definition, the correct name
is TARGET_PPC instead of TARGET_POWERPC.
On Wed, Jan 05, 2011 at 01:36:35PM +0100, Jes Sorensen wrote:
On 01/05/11 13:34, Michael S. Tsirkin wrote:
On Wed, Jan 05, 2011 at 11:41:02AM +0100, jes.soren...@redhat.com wrote:
From: Jes Sorensen jes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
On 01/05/2011 04:41 AM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
architectures. Otherwise qemu-img will fail to create disk
images= 2GB
Signed-off-by: Jes Sorensenjes.soren...@redhat.com
off_t would be
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of
On 01/05/11 14:46, Anthony Liguori wrote:
On 01/05/2011 04:41 AM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
architectures. Otherwise qemu-img will fail to create disk
images= 2GB
Signed-off-by: Jes
** Changed in: linux (Ubuntu)
Status: Invalid = Triaged
** Changed in: qemu-kvm (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
** Changed in: qemu-kvm (Ubuntu)
Status: In Progress = Invalid
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Serge
The bug is still there so I rediffed the old patch against current
code.
On a related topic: could somebody give me advice on how to implement
a command line (command line seems enough, the other option would be
monitor command) to make the MADV_MERGEABLE conditional? I got KSM on
THP working
** Description changed:
Binary package hint: qemu
Guest kernel hang during boot when KVM is active on i386 host
- See the patch.
+ See the patch.
http://www.spinics.net/lists/kvm/msg40800.html
How to reproduce:
1. install Maversick x86 (not amd64)
2. ensure you have kvm
Juan Quintela quint...@redhat.com writes:
We need to invalidate the Read Cache on the destination, otherwise we
have corruption. Easy way to reproduce it is:
- create an qcow2 images
- start qemu on destination of migration (qemu -incoming tcp:...)
- start qemu on source of migration
On Tue, Nov 30, 2010 at 02:26:01PM +0100, Gerd Hoffmann wrote:
Hi,
This patch series adds a flag which allows pci devices being tagged
as not hotpluggable. It also sets this flag for a number of devices.
cheers,
Gerd
Gerd Hoffmann (3):
pci: allow devices being tagged as not
On Wed, Dec 08, 2010 at 03:11:36PM -0200, Marcelo Tosatti wrote:
On top of add hotplug opt-out option for devices patchset
http://www.mail-archive.com/qemu-devel@nongnu.org/msg46953.html.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
I put this patchset on my tree - want me to queue
On Wed, Jan 05, 2011 at 06:00:00PM +0200, Michael S. Tsirkin wrote:
On Wed, Dec 08, 2010 at 03:11:36PM -0200, Marcelo Tosatti wrote:
On top of add hotplug opt-out option for devices patchset
http://www.mail-archive.com/qemu-devel@nongnu.org/msg46953.html.
Signed-off-by: Marcelo
On Tue, Jan 04, 2011 at 09:32:12AM +0100, Jan Kiszka wrote:
Next round, addressing review comments and new findings:
- new: Flush coalesced mmio buffer on IO window exits
- new: Do not use qemu_fair_mutex in kvm mode
- new: Implicitly clear nmi_injected/pending on reset
- new: Fix
On 01/04/2011 03:39 PM, Marcelo Tosatti wrote:
On Tue, Jan 04, 2011 at 08:17:26AM -0600, Anthony Liguori wrote:
On 01/03/2011 04:01 AM, Avi Kivity wrote:
On 01/03/2011 11:46 AM, Jan Kiszka wrote:
Hi,
at least in kvm mode, the qemu_fair_mutex seems to have lost its
function
On 02.01.2011, at 13:06, Aurelien Jarno wrote:
Use the new function float32_is_any_nan() instead of
float32_is_quiet_nan() || float32_is_signaling_nan().
Cc: Alexander Graf ag...@suse.de
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
I frankly have very little knowledge of FP stuff.
Hi,
I don't see this patch in the git tree, nor a revert of the buggy
commit. Was any decision made on this?
thanks,
-serge
On Thu, 23 Dec 2010, Paolo Bonzini wrote:
The polling nature of the USB HID device makes it very hard to double
click or drag while on a high-latency VNC connection. This patch,
based on work done in the Xen qemu-dm tree by Ian Jackson, fixes this
bug by adding an event queue to the device.
On 01/05/2011 06:44 PM, Anthony Liguori wrote:
On 01/04/2011 03:39 PM, Marcelo Tosatti wrote:
On Tue, Jan 04, 2011 at 08:17:26AM -0600, Anthony Liguori wrote:
On 01/03/2011 04:01 AM, Avi Kivity wrote:
On 01/03/2011 11:46 AM, Jan Kiszka wrote:
Hi,
at least in kvm mode, the qemu_fair_mutex
On 02.01.2011, at 15:39, Aurelien Jarno wrote:
On PPC the default qNaN doesn't have the sign bit set.
The spec says don't care for the sign bit. Did you extract the value
empirically? I'm not saying it's wrong - the default 32 Bit value seems to be
0x7FC0_ (2.06 ISA 6.6.2.2).
Hrm ...
On 02.01.2011, at 15:39, Aurelien Jarno wrote:
The PRECISE_EMULATION is hardcoded to one in target-ppc/exec.h and not
something easily tunable. Remove it and non-precise emulation code as
it doesn't make a noticeable difference in speed. People wanting speed
improvement should use
On 5 January 2011 16:59, Alexander Graf ag...@suse.de wrote:
On 02.01.2011, at 13:06, Aurelien Jarno wrote:
Use the new function float32_is_any_nan() instead of
float32_is_quiet_nan() || float32_is_signaling_nan().
Cc: Alexander Graf ag...@suse.de
Signed-off-by: Aurelien Jarno
On Sun, Jan 02, 2011 at 01:06:49PM +0100, Aurelien Jarno wrote:
Use the new function float32_is_any_nan() instead of
float32_is_quiet_nan() || float32_is_signaling_nan().
Cc: Alexander Graf ag...@suse.de
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
Reviewed-by: Nathan Froyd
On 05.01.2011, at 18:14, Peter Maydell wrote:
On 5 January 2011 16:59, Alexander Graf ag...@suse.de wrote:
On 02.01.2011, at 13:06, Aurelien Jarno wrote:
Use the new function float32_is_any_nan() instead of
float32_is_quiet_nan() || float32_is_signaling_nan().
Cc: Alexander Graf
On 02.01.2011, at 15:39, Aurelien Jarno wrote:
The current FPU code returns 0.0 if one of the operand is a
signaling NaN and the VXSNAN exception is disabled.
fload_invalid_op_excp() doesn't return a qNaN in case of a VXSNAN
exception as the operand should be propagated instead of a new
On 03.01.2011, at 15:34, Aurelien Jarno wrote:
Implement the correct NaN propagation rules for ARM targets by
providing an appropriate pickNaN function.
Also fix the #ifdef tests for default NaN definition, the correct name
is TARGET_PPC instead of TARGET_POWERPC.
Cc: Alexander Graf
Hi Chunqiang,
On 01/04/2011 03:44 PM, Chunqiang Tang wrote:
Dear QEMU Community Members,
Happy new year! We would like to contribute a new year gift to the
community.
As the community considers the next-generation image formats for QEMU,
hopefully we really challenge ourselves hard enough to
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
The bug is still there so I rediffed the old patch against current
code.
On a related topic: could somebody give me advice on how to implement
a command line (command line seems enough, the other option would be
monitor command) to make the
On 01/05/2011 08:40 AM, Jes Sorensen wrote:
On 01/05/11 14:46, Anthony Liguori wrote:
On 01/05/2011 04:41 AM, jes.soren...@redhat.com wrote:
From: Jes Sorensenjes.soren...@redhat.com
strtosz() needs to return a 64 bit type even on 32 bit
architectures. Otherwise qemu-img will fail
* Ryan Harper ry...@us.ibm.com [2011-01-04 09:49]:
* Aurelien Jarno aurel...@aurel32.net [2010-12-25 16:37]:
On Wed, Dec 08, 2010 at 04:27:45PM -0200, Luiz Capitulino wrote:
On Wed, 08 Dec 2010 12:23:12 -0600
Anthony Liguori aligu...@linux.vnet.ibm.com wrote:
On 12/08/2010 12:01
On 01/05/11 19:29, Anthony Liguori wrote:
I wouldn't make such bold claims but I'll concede that one is not
significantly better than the other and won't object to int64_t if you
feel strongly.
The more I think of it, the more I come to the conclusion that int64_t
is the best solution. Since
On Wed, Dec 08, 2010 at 03:11:36PM -0200, Marcelo Tosatti wrote:
On top of add hotplug opt-out option for devices patchset
http://www.mail-archive.com/qemu-devel@nongnu.org/msg46953.html.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff --git a/hw/acpi_piix4.c b/hw/acpi_piix4.c
On Tue, Nov 30, 2010 at 02:26:03PM +0100, Gerd Hoffmann wrote:
This patch tags all pci devices which belong to the piix3/4 chipsets as
not hotpluggable (Host bridge, ISA bridge, IDE controller, ACPI bridge).
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/acpi_piix4.c |2 ++
On 05.01.2011, at 19:02, Michael Roth wrote:
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
The bug is still there so I rediffed the old patch against current
code.
On a related topic: could somebody give me advice on how to implement
a command line (command line seems enough, the other
** Patch added: Kernel patch against ubuntu-maverick kernel fixing this issue
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/688085/+attachment/1784370/+files/0001-UBUNTU-Upstream-KVM-x86-emulator-fix-regression-with.patch
--
You received this bug notification because you are a member
On Tue, Jan 04, 2011 at 10:57:08AM +0530, Arun R Bharadwaj wrote:
@@ -545,13 +555,19 @@ static void paio_cancel(BlockDriverAIOCB *blockacb)
}
mutex_unlock(lock);
-if (active) {
-/* fail safe: if the aio could not be canceled, we wait for
- it */
-
On Tue, Jan 04, 2011 at 10:57:20AM +0530, Arun R Bharadwaj wrote:
+static void aio_thread(ThreadletWork *work)
+{
aio_thread() is not a descriptive name here. This isn't the top-level
thread function, just the work-func. Please choose something like
handle_aiocb() or handle_work().
+
On Tue, Jan 04, 2011 at 10:57:49AM +0530, Arun R Bharadwaj wrote:
Remove thread_create and use qemu_thread_create instead.
Signed-off-by: Arun R Bharadwaj a...@linux.vnet.ibm.com
---
posix-aio-compat.c | 19 ++-
1 files changed, 2 insertions(+), 17 deletions(-)
Can we
On Tue, Jan 04, 2011 at 10:57:39AM +0530, Arun R Bharadwaj wrote:
@@ -574,33 +574,39 @@ static void paio_remove(struct qemu_paiocb *acb)
}
}
-static void paio_cancel(BlockDriverAIOCB *blockacb)
+/**
+ * dequeue_work: Cancel a task queued on the global queue.
+ * @work: Contains the
Hello everyone,
On Wed, Jan 05, 2011 at 08:44:38PM +0100, Alexander Graf wrote:
On 05.01.2011, at 19:02, Michael Roth wrote:
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
The bug is still there so I rediffed the old patch against current
code.
On a related topic: could somebody
On Tue, Jan 04, 2011 at 10:57:27AM +0530, Arun R Bharadwaj wrote:
@@ -66,15 +81,10 @@ typedef struct PosixAioState {
struct qemu_paiocb *first_aio;
} PosixAioState;
-
-static pthread_mutex_t lock = PTHREAD_MUTEX_INITIALIZER;
-static pthread_cond_t cond = PTHREAD_COND_INITIALIZER;
On 05.01.2011, at 20:54, Andrea Arcangeli wrote:
Hello everyone,
On Wed, Jan 05, 2011 at 08:44:38PM +0100, Alexander Graf wrote:
On 05.01.2011, at 19:02, Michael Roth wrote:
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
The bug is still there so I rediffed the old patch against
On 01/05/2011 01:44 PM, Alexander Graf wrote:
On 05.01.2011, at 19:02, Michael Roth wrote:
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
The bug is still there so I rediffed the old patch against current
code.
On a related topic: could somebody give me advice on how to implement
On 01/05/2011 02:00 PM, Alexander Graf wrote:
On 05.01.2011, at 20:54, Andrea Arcangeli wrote:
Hello everyone,
On Wed, Jan 05, 2011 at 08:44:38PM +0100, Alexander Graf wrote:
On 05.01.2011, at 19:02, Michael Roth wrote:
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
On Wed, Jan 05, 2011 at 09:00:45PM +0100, Alexander Graf wrote:
Sure, not all combinations make sense. But -mem
size=1G,path=/dev/shm/vm1.ram,populate=on would make sense, no? TPH
I was referring to Michael's suggestion, sure many options make sense
for mem-path too, in fact populate makes more
On 01/05/2011 01:54 PM, Andrea Arcangeli wrote:
Hello everyone,
On Wed, Jan 05, 2011 at 08:44:38PM +0100, Alexander Graf wrote:
On 05.01.2011, at 19:02, Michael Roth wrote:
On 01/05/2011 09:10 AM, Andrea Arcangeli wrote:
The bug is still there so I rediffed the old patch against current
On Wed, Jan 05, 2011 at 02:26:19PM -0600, Michael Roth wrote:
Yah you're right, but I've seen several discussions about using mempath
for tmpfs/ram-backed files for things like numa/zram/etc so tend to
think of it as something potentially more than just a hook for
hugetlbfs, which is
On 01/05/2011 02:35 PM, Andrea Arcangeli wrote:
On Wed, Jan 05, 2011 at 02:26:19PM -0600, Michael Roth wrote:
Yah you're right, but I've seen several discussions about using mempath
for tmpfs/ram-backed files for things like numa/zram/etc so tend to
think of it as something potentially more
Hi,
Am 02.01.2011 um 19:44 schrieb Hervé Poussineau:
This unregresses Sun4m and PPC prep/ref405ep machines
Signed-off-by: Hervé Poussineau hpous...@reactos.org
Were there any visible symptoms of the regression? Or did you just
spot this while reading the code?
Patch itself looks
On Wed, Jan 05, 2011 at 11:21:06AM +0100, Aurelien Jarno wrote:
But that's not the subject we are talking about HPPA guest support.
target-hppa fork still (partially) uses dyngen code, which we don't
support in upstream for more than *2 years*.
I'd agree -- the fork is currently dead.
On Wed, Jan 05, 2011 at 01:10:08PM +0200, Gleb Natapov wrote:
On Wed, Dec 08, 2010 at 03:08:59PM -0200, Marcelo Tosatti wrote:
Use _RMV method to indicate whether device can be removed.
Data is retrieved from QEMU via I/O port 0xae0c.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
80 matches
Mail list logo
