Am 15.09.2013 02:03, schrieb Richard Henderson:
The function was deleted in 4dc81f2822187f4503d4bdb76785cafa5b28db0b.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/tcg.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/tcg/tcg.h b/tcg/tcg.h
index 902c751..20543f6 100644
---
On Fri, Sep 13, 2013 at 01:58:44PM +0200, Hervé Poussineau wrote:
This check is useless, as bigger addresses will be ignored when
added to 'io' MemoryRegion, which has a size of 64K.
However, some architectures don't use the 'io' MemoryRegion, like
the alpha and versatile platforms. They
Am 15.09.2013 02:03, schrieb Richard Henderson:
Slightly changes the interface, in that we now return name
instead of a TCGHelperInfo structure, which goes away.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/tcg.c | 74
Am 15.09.2013 02:03, schrieb Richard Henderson:
This brings the m68k target in line with all other targets.
Signed-off-by: Richard Henderson r...@twiddle.net
---
target-m68k/helper.c| 2 +-
target-m68k/{helpers.h = helper.h} | 0
target-m68k/op_helper.c | 2 +-
On Sun, 2013-09-15 at 00:08 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 02:21:36PM +0300, Marcel Apfelbaum wrote:
Created a MemoryRegion with negative priority that
spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will
On Fri, Sep 13, 2013 at 07:29:49PM -, Vasile Dumitrescu wrote:
I also see these EXACT symptoms, using kvm (VM managed through livirt
virsh) on Debian x64 host, guest is Windows 8, RedHat VirtIo network
driver.
Can you trace KVM [1] when hang happens next time?
[1]
Am 15.09.2013 02:03, schrieb Richard Henderson:
During GEN_HELPER=1, these are actually stray top-level semi-colons
which are technically invalid ISO C, but GCC accepts as an extension.
If we added enough __extension__ markers that we could dare use
-Wpedantic, we'd see
warning: ISO C does
Il 14/09/2013 11:24, Erik Rull ha scritto:
Hi all,
I tried a guest OS that is ACPI capable with enabled ACPI in qemu (+kvm)
and qemu quits when the guest OS was shut down (and the guest PC
should be powered off). Well, from the guest point of view, this
behavior seems to be okay, but I
On Tue, Sep 10, 2013 at 02:12:56PM +0100, Peter Maydell wrote:
On 10 September 2013 14:02, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Sep 10, 2013 at 01:50:47PM +0100, Peter Maydell wrote:
On 10 September 2013 13:39, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at
Michael S. Tsirkin a écrit :
On Fri, Sep 13, 2013 at 01:58:44PM +0200, Hervé Poussineau wrote:
This check is useless, as bigger addresses will be ignored when
added to 'io' MemoryRegion, which has a size of 64K.
However, some architectures don't use the 'io' MemoryRegion, like
the alpha and
w32/w64 properties that we report in QOM are
currently static, but this is wrong:
guest firmware can select its own windows:
optimal placement for w64 is guest-dependent, further,
for Q35, w32 is affected by the MCFG base and size.
This detects the actual window configuration used by guest
and
will help simplify header dependencies.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
include/qemu/range.h| 2 +-
include/qemu/typedefs.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/qemu/range.h b/include/qemu/range.h
index b76cc0d..4a0780d 100644
---
For Q35, MMCFG address and size are guest configurable.
Update w32 property to make it behave accordingly.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/pci-host/q35.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/hw/pci-host/q35.c b/hw/pci-host/q35.c
index
Detect the 64 bit window programmed by firmware
and configure properties accordingly.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/pci-host/q35.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/hw/pci-host/q35.c b/hw/pci-host/q35.c
index
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
include/hw/pci/pci.h | 1 +
hw/pci/pci.c | 50 ++
2 files changed, 51 insertions(+)
diff --git a/include/hw/pci/pci.h b/include/hw/pci/pci.h
index 37979aa..4b90e5d 100644
---
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
include/qemu/range.h | 17 +
1 file changed, 17 insertions(+)
diff --git a/include/qemu/range.h b/include/qemu/range.h
index 4a0780d..1c688ca 100644
--- a/include/qemu/range.h
+++ b/include/qemu/range.h
@@ -17,6 +17,23 @@
Detect the 64 bit window programmed by firmware
and configure properties accordingly.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/pci-host/piix.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
index
On Sun, Sep 15, 2013 at 11:46:44AM +0300, Michael S. Tsirkin wrote:
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Actually I applied the following on top - not going to
repost as that just adds a comment.
diff --git a/include/qemu/range.h b/include/qemu/range.h
index 1c688ca..aae9720 100644
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
On Tue, 2013-09-10 at 14:12 +0100, Peter Maydell wrote:
On 10 September 2013 14:02, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Sep 10, 2013 at 01:50:47PM +0100, Peter Maydell wrote:
On 10 September 2013 13:39, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at
On 14 September 2013 18:35, Stefan Weil s...@weilnetz.de wrote:
All (?) syscalls fail to handle addresses larger than 32 bit correctly.
See Bad address in the strace ouput below.
Isn't 64 bit guest on 32 bit host in the set of things we don't
expect to work ? Maybe I'm misremembering...
-- PMM
On 14 September 2013 22:31, Michael S. Tsirkin m...@redhat.com wrote:
Enabling the print in memory.c shows quite a lot
of these:
warning: subregion collision fec0/1000 (ioapic) vs 800/f800
(pci-hole)
warning: subregion collision fed0/400 (hpet) vs 800/f800
(pci-hole)
On 15 September 2013 08:03, Stefan Weil s...@weilnetz.de wrote:
Instead of removing the semicolons from the DEF_HELPER_x lines,
I'd prefer removing them from the DEF_HELPER_FLAGS_x definitions.
Code formatters and static code analyzers (maybe humans, too) prefer
lines which look like valid C
On Fri, Sep 13, 2013 at 04:49:48PM +0200, Paolo Bonzini wrote:
I'm not sure of the benefit of an hw/ipack directory if (a) there is
only one class providing the bus and (b) all the classes using the
bus (well, there is just one of them) are in the same directory.
If any of the two
On Fri, Sep 06, 2013 at 03:30:38PM +0200, Christian Borntraeger wrote:
On 06/09/13 14:19, Jens Freimann wrote: This series adds a kvm_device that
acts as a irq controller for floating
interrupts. As a first step it implements functionality to retrieve and
inject
interrupts for the
On 15 September 2013 08:14, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Sep 10, 2013 at 02:12:56PM +0100, Peter Maydell wrote:
On 10 September 2013 14:02, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Sep 10, 2013 at 01:50:47PM +0100, Peter Maydell wrote:
On 10 September 2013
On Sun, Sep 15, 2013 at 11:56:40AM +0100, Peter Maydell wrote:
On 15 September 2013 08:14, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Sep 10, 2013 at 02:12:56PM +0100, Peter Maydell wrote:
On 10 September 2013 14:02, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Sep 10, 2013 at
On 15 September 2013 12:05, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 11:56:40AM +0100, Peter Maydell wrote:
The alias will win for the addresses it handles. But if
the alias is a container with holes then it doesn't handle
the holes and the lower priority background
On Sun, Sep 15, 2013 at 12:23:41PM +0100, Peter Maydell wrote:
On 15 September 2013 12:05, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 11:56:40AM +0100, Peter Maydell wrote:
The alias will win for the addresses it handles. But if
the alias is a container with holes
On 15 September 2013 13:17, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 12:23:41PM +0100, Peter Maydell wrote:
. If it's a pure container then it
doesn't respond for areas that none of its subregions
cover (it can't, it has no idea what it should do).
Interesting. This
On Sun, Sep 15, 2013 at 02:24:07PM +0100, Peter Maydell wrote:
On 15 September 2013 13:17, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 12:23:41PM +0100, Peter Maydell wrote:
. If it's a pure container then it
doesn't respond for areas that none of its subregions
cover
On 15 September 2013 14:39, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 02:24:07PM +0100, Peter Maydell wrote:
Yes, that's true, but even then it's usually just overlaps
of subregions within a single container and there isn't
a need to worry about within-container versus
On Sun, Sep 15, 2013 at 02:49:32PM +0100, Peter Maydell wrote:
On 15 September 2013 14:39, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 02:24:07PM +0100, Peter Maydell wrote:
Yes, that's true, but even then it's usually just overlaps
of subregions within a single
On 15 September 2013 15:08, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 02:49:32PM +0100, Peter Maydell wrote:
Yes, but if we were applying a sensible set of priorities
then you don't need to care at all about the contents
of the pci hole container, because the pci hole
On Sun, Sep 15, 2013 at 03:08:38PM +0100, Peter Maydell wrote:
On 15 September 2013 15:08, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 02:49:32PM +0100, Peter Maydell wrote:
Yes, but if we were applying a sensible set of priorities
then you don't need to care at all
On 15 September 2013 15:20, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:08:38PM +0100, Peter Maydell wrote:
Well, that's your choice, but I'd be really surprised if the
PCI controller allowed PCI BARs to get mapped over the
top of builtin devices like that.
Well it
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite common for developers trying to understand
how the memory region system works, so expand and clarify it.
This includes a worked example
On Sun, Sep 15, 2013 at 03:49:00PM +0100, Peter Maydell wrote:
On 15 September 2013 15:20, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:08:38PM +0100, Peter Maydell wrote:
Well, that's your choice, but I'd be really surprised if the
PCI controller allowed PCI BARs to
On 15 September 2013 16:05, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:49:00PM +0100, Peter Maydell wrote:
On 15 September 2013 15:20, Michael S. Tsirkin m...@redhat.com wrote:
Actually you previosly wrote:
the versatilePB's PCI controller only responds to
On Sun, Sep 15, 2013 at 03:51:53PM +0100, Peter Maydell wrote:
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite common for developers trying to understand
how the memory region system
On Sun, Sep 15, 2013 at 04:08:26PM +0100, Peter Maydell wrote:
On 15 September 2013 16:05, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:49:00PM +0100, Peter Maydell wrote:
On 15 September 2013 15:20, Michael S. Tsirkin m...@redhat.com wrote:
Actually you previosly
A MemoryRegion with negative priority was created and
it spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will follow the pci spec:
1. returns -1 on read
2. does nothing on write
Note: setting the RECEIVED MASTER ABORT bit in the STATUS
PCI spec requires that a transaction that has not been claimed
by any PCI bus devices will be terminated by the initiator
with master abort. For read transactions -1() is returned and
writes are silently dropped.
Implementation:
- Allowed the MemoryRegion priority to be negative so a
Priority was used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be visible on all the addresses not covered
by other subregions.
Signed-off-by:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be visible on all the addresses not covered
by the parent MemoryRegion or other
On 09/11/2013 07:54:32 AM, Claudio Fontana wrote:
This is the aarch64 libvixl support patchset in the current state.
It provides (limited) support for disassembly output on aarch64.
Only host disassembly is enabled, since target for aarch64 is not in
yet.
An external objdump solution as
On 15 September 2013 16:24, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:51:53PM +0100, Peter Maydell wrote:
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite
On Sun, Sep 15, 2013 at 05:55:54PM +0100, Peter Maydell wrote:
On 15 September 2013 16:24, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:51:53PM +0100, Peter Maydell wrote:
The documentation of how overlapping memory regions behave and how
the priority system works
On 15 September 2013 16:31, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 04:08:26PM +0100, Peter Maydell wrote:
The aborts I refer to above are if you misprogram the
device to try to do a bus master access to some part of
PCI memory space other than where the host
On Sun, Sep 15, 2013 at 07:16:39PM +0300, Marcel Apfelbaum wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be visible
Add a helper macro for adding read-only properties, that works in the
common case where the value is a constant.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
I'm using this patch in my acpi work - any objections
to applying it on my tree?
include/qom/object.h | 21
On 15 September 2013 17:16, Marcel Apfelbaum marce...@redhat.com wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be
On 15 September 2013 17:41, Rob Landley r...@landley.net wrote:
Wait, incorporating C++ code into qemu was considered the _good_ solution?
What was the bad solution?
Not supporting disassembly at all, and/or having a runtime
dependency on finding an objdump that works for the target.
-- PMM
On Sun, Sep 15, 2013 at 07:16:41PM +0300, Marcel Apfelbaum wrote:
A MemoryRegion with negative priority was created and
it spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will follow the pci spec:
1. returns -1 on read
2. does nothing on
On 15 September 2013 18:07, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 05:55:54PM +0100, Peter Maydell wrote:
On 15 September 2013 16:24, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 03:51:53PM +0100, Peter Maydell wrote:
The memory core uses the
On 15 September 2013 18:30, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 07:16:41PM +0300, Marcel Apfelbaum wrote:
+static const MemoryRegionOps master_abort_mem_ops = {
+.read = master_abort_mem_read,
+.write = master_abort_mem_write,
+.endianness =
On 15 September 2013 17:16, Marcel Apfelbaum marce...@redhat.com wrote:
Priority was used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be
On Sun, Sep 15, 2013 at 06:29:51PM +0100, Peter Maydell wrote:
On 15 September 2013 18:07, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 05:55:54PM +0100, Peter Maydell wrote:
On 15 September 2013 16:24, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at
On 15 September 2013 18:25, Peter Maydell peter.mayd...@linaro.org wrote:
On 15 September 2013 17:16, Marcel Apfelbaum marce...@redhat.com wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
If you have to do a
On 15 September 2013 18:23, Michael S. Tsirkin m...@redhat.com wrote:
+/* Add a property that is an integer constant. */
+#define OBJECT_ADD_PROP_CONST(obj, name, value) \
+do {\
+void
Le Friday 06 Sep 2013 à 11:55:38 (+0200), Kevin Wolf a écrit :
Am 06.09.2013 um 11:18 hat Fam Zheng geschrieben:
On Fri, 09/06 10:45, Kevin Wolf wrote:
Am 06.09.2013 um 09:56 hat Fam Zheng geschrieben:
Since BlockDriver.bdrv_snapshot_create() is an optional operation,
blockdev.c
Kevin what do you think of this ?
I could strip down the dedupe journal code to specialize it.
If you think it turns out easier than using the journalling
infrastructure that we're going to implement anyway, then why not.
This question need to be though.
The good thing about the current
On Sun, 2013-09-15 at 20:30 +0300, Michael S. Tsirkin wrote:
On Sun, Sep 15, 2013 at 07:16:41PM +0300, Marcel Apfelbaum wrote:
A MemoryRegion with negative priority was created and
it spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will
On Sun, 2013-09-15 at 18:32 +0100, Peter Maydell wrote:
On 15 September 2013 18:30, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 07:16:41PM +0300, Marcel Apfelbaum wrote:
+static const MemoryRegionOps master_abort_mem_ops = {
+.read = master_abort_mem_read,
+
On Sun, Sep 15, 2013 at 7:27 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 15 September 2013 17:41, Rob Landley r...@landley.net wrote:
Wait, incorporating C++ code into qemu was considered the _good_ solution?
What was the bad solution?
Not supporting disassembly at all, and/or
On Sun, Sep 15, 2013 at 06:54:35PM +0100, Peter Maydell wrote:
On 15 September 2013 18:23, Michael S. Tsirkin m...@redhat.com wrote:
+/* Add a property that is an integer constant. */
+#define OBJECT_ADD_PROP_CONST(obj, name, value) \
+do {
On Sun, Sep 15, 2013 at 06:32:13PM +0100, Peter Maydell wrote:
On 15 September 2013 18:30, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 07:16:41PM +0300, Marcel Apfelbaum wrote:
+static const MemoryRegionOps master_abort_mem_ops = {
+.read = master_abort_mem_read,
On 15 September 2013 21:25, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 06:32:13PM +0100, Peter Maydell wrote:
On 15 September 2013 18:30, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 07:16:41PM +0300, Marcel Apfelbaum wrote:
+static const
On Sun, Sep 15, 2013 at 09:40:37PM +0100, Peter Maydell wrote:
On 15 September 2013 21:25, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 06:32:13PM +0100, Peter Maydell wrote:
On 15 September 2013 18:30, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at
On 15 September 2013 22:07, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Sep 15, 2013 at 09:40:37PM +0100, Peter Maydell wrote:
native means if the device's MMIO callback does 'return 0x12345678;'
for a 32 bit read then the guest CPU should see 0x12345678. That's
almost always what you
On Fri, 09/13 15:07, Daniel P. Berrange wrote:
On Fri, Sep 13, 2013 at 05:59:13PM +0800, Fam Zheng wrote:
+void module_load(module_load_type type)
+{
+#ifdef CONFIG_MODULES
+const char *path;
+char *fname = NULL;
+const char **mp;
+const char *module_whitelist[] = {
On Fri, 09/13 12:31, Peter Maydell wrote:
On 13 September 2013 10:59, Fam Zheng f...@redhat.com wrote:
This series implements feature of shared object building as described in:
http://wiki.qemu.org/Features/Modules
This doesn't seem to apply to master:
cam-vm-266:precise:qemu$ patches
On Fri, 09/13 07:52, Richard Henderson wrote:
On 09/13/2013 02:59 AM, Fam Zheng wrote:
+const char *module_whitelist[] = {
+CONFIG_MODULE_WHITELIST
+};
static const char * const module_whitelist[] = ...
OK, thanks.
+switch (type) {
+case
In struct APICCommonState, there is an id field yet, which was set earlier,
qdev_prop_set_uint8(env-apic_state, id, env-cpuid_apic_id);
so we use the id field instead of the variable 'apic_no' to represent the
unique apic
index.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/i386/pc.c | 6 ++
hw/i386/pc_piix.c| 1 +
include/hw/boards.h | 2 ++
include/hw/i386/pc.h | 1 +
qapi-schema.json | 12
qmp-commands.hx | 23 +++
qmp.c| 9
This motion is preparing for refactoring vCPU apic subsequently.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
cpu-exec.c| 2 +-
cpus.c| 5 ++---
hw/i386/kvmvapic.c| 8 +++-
hw/i386/pc.c | 17 -
Via implementing ACPI standard methods _EJ0 in bios, after Guest OS hot remove
one vCPU, it is able to send a signal to QEMU, then QEMU could notify
the assigned vCPU of exiting. meanwhile, and intruduce the QOM command
'cpu-del' to remove
vCPU from QEMU itself.
this work is based on Andreas
When OS eject a vcpu (like: echo 1 /sys/bus/acpi/devices/LNXCPUXX/eject),
it will call acpi EJ0 method, the firmware will write the new cpumap, QEMU
will know which vcpu need to be ejected.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/acpi/piix4.c | 37
Rename variable 'cpu_added_notifier' to 'cpu_hotplug_notifier', for
adding vcpu-remove notifier support.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/acpi/piix4.c | 10 +-
hw/i386/pc.c| 2 +-
include/sysemu/sysemu.h | 2 +-
qom/cpu.c |
Using CPU_FOREACH() marco instead of scaning the entire
local_apics array for fast searching apic.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/intc/apic.c | 73 ++---
include/hw/i386/apic_internal.h | 2 --
2 files changed, 32
Move struct HotplugEventType from file piix4.c to file qom/cpu.c,
and add struct CPUNotifier for supporting UNPLUG cpu notifier.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/acpi/piix4.c | 8 ++--
include/qom/cpu.h | 10 ++
qom/cpu.c | 6 +-
3 files
After ACPI get a signal to eject a vCPU, then it will notify
the vCPU thread to exit in KVM, and the vCPU must be removed from CPU list，
before the vCPU really removed, there will release the all related vCPU objects.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
cpus.c
Implement x86_cpu_unrealizefn() for corresponding x86_cpu_realizefn(),
which is mostly used to clear the apic related information at here.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/i386/kvm/apic.c| 8
hw/intc/apic.c| 8
target-i386/cpu-qom.h | 1
Implement cpu interface pc_hot_del_cpu() for unrealizing device vCPU.
emiting vcpu-remove notifier to ACPI, then ACPI could send sci interrupt
to OS for hot-remove vcpu.
Signed-off-by: Chen Fan chen.fan.f...@cn.fujitsu.com
---
hw/i386/pc.c | 30 --
qom/cpu.c| 12
On 09/10/2013 02:26 PM, Alexey Kardashevskiy wrote:
On 09/04/2013 12:56 PM, Alexey Kardashevskiy wrote:
On 08/30/2013 03:28 PM, Alexey Kardashevskiy wrote:
Yet another try with XICS and XICS-KVM.
v3-v4:
Addressed multiple comments from Alex;
Split out many tiny patches to make them easier
于 2013/9/12 17:31, Paolo Bonzini 写道:
Il 12/09/2013 11:15, Wenchao Xia ha scritto:
This series will remove the usage of symbols of mon-protocol-event in
qemu-img, qemu-nbd and qemu-io, in short remove the connetion for block
layer.
Background:
I am tring to decouple block layer code with
Hi,
I want to use a ram disk as a block device for my kernel.( i am
measuring file io on ram )
I am trying to boot a kernel from using /dev/ram0. However I am getting
No root Device found
qemu-system-x86_64 -m 8G -hda disk.img -kernel vmlinuz-3.10.0-rc6
-initrd
On 13.09.2013 17:20, Kevin Wolf wrote:
Am 13.09.2013 um 10:25 hat Paolo Bonzini geschrieben:
Il 13/09/2013 09:33, Peter Lieven ha scritto:
On 06.09.2013 17:39, Stefan Hajnoczi wrote:
From: Paolo Bonzini pbonz...@redhat.com
If the sectors are unallocated and we are past the end of the
backing
On 13.09.2013 12:25, Peter Lieven wrote:
this patch does 2 things:
a) only do additional call outs if BDRV_BLOCK_ZERO is not already set.
b) use bdi.discard_zeroes to return the zero state of an unallocated block.
the callout to bdrv_has_zero_init() is only valid right after bdrv_create.
89 matches
Mail list logo
