Am 11.05.2015 um 21:08 schrieb Jim Fehlig:
The generated AUTHORS file contains many duplicates. If an author
has N commits, there will be N entries for the author in AUTHORS.
Check if an author already exists in the list before appending.
Reported-by: Andreas Färber afaer...@suse.de
Am 13.03.2015 um 20:45 schrieb Eduardo Habkost:
On Fri, Mar 13, 2015 at 08:25:19PM +0100, Andreas Färber wrote:
Only thing that comes to mind is whether it might make sense to
hierarchically make Broadwell the parent type of Broadwell-noTSX, to
avoid duplication. But then again we already have
Am 13.03.2015 um 20:09 schrieb Eduardo Habkost:
With the Intel microcode update that removed HLE and RTM, there will be
different kinds of Haswell and Broadwell CPUs out there: some that still
have the HLE and RTM features, and some that don't have the HLE and RTM
features. On both cases
Am 22.09.2014 um 15:05 schrieb Alex Bligh:
Sadly that is not true. For instance on Ubuntu Precise
it's invoked as qemu-system-x86_64 by at least one
management application known to me.
Well change it to call qemu-kvm then :)
Also what happens if you install qemu as well?
Does it conflict?
Hi Alex,
+ quintela, mst, libvirt
Am 22.07.2014 20:43, schrieb Alex Bligh:
Add a machine type pc-1.0-qemu-kvm for live migrate compatibility
with qemu-kvm version 1.0.
Signed-off-by: Alex Bligh a...@alex.org.uk
---
hw/acpi/piix4.c | 49
Am 15.05.2014 14:35, schrieb Igor Mammedov:
PS:
As side effect cpu/apic will disappear from info qtree HMP command output.
Solutions are already on the list and in need of feedback:
http://patchwork.ozlabs.org/patch/317224/
http://patchwork.ozlabs.org/patch/343136/
Am 15.05.2014 15:07, schrieb Eduardo Habkost:
On Thu, May 15, 2014 at 02:35:01PM +0200, Igor Mammedov wrote:
On Tue, 06 May 2014 22:29:24 +0200
Andreas Färber afaer...@suse.de wrote:
Am 06.05.2014 22:19, schrieb Eduardo Habkost:
On Tue, May 06, 2014 at 10:01:11PM +0200, Igor Mammedov wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.05.2014 19:05, schrieb Eric Blake:
[adding libvirt]
On 05/09/2014 05:54 AM, Gerd Hoffmann wrote:
Hi,
virt-manager/libvirt seems to default to 9 MByte of Vram for
cirrus, so this would break a lot of setups.
It wouldn't. libvirt
Am 06.05.2014 22:19, schrieb Eduardo Habkost:
On Tue, May 06, 2014 at 10:01:11PM +0200, Igor Mammedov wrote:
On Tue, 6 May 2014 11:42:56 -0300
Eduardo Habkost ehabk...@redhat.com wrote:
On Tue, May 06, 2014 at 09:22:38AM +0200, Igor Mammedov wrote:
On Fri, 2 May 2014 11:43:05 -0300
Eduardo
Am 11.02.2014 16:58, schrieb Anthony Liguori:
On Tue, Feb 11, 2014 at 7:25 AM, Eduardo Habkost ehabk...@redhat.com wrote:
On Tue, Feb 11, 2014 at 06:31:35AM -0800, Anthony Liguori wrote:
On Fri, Feb 7, 2014 at 2:55 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 07/02/2014 11:16, Eduardo
Am 10.02.2014 11:21, schrieb Eduardo Habkost:
+static const TypeInfo x86_cpu_host_type_info = {
+.name = CPU_CLASS_NAME(host),
+.parent = TYPE_X86_CPU,
+.instance_size = sizeof(X86CPU),
+.instance_init = x86_cpu_instance_init_host,
+.abstract = false,
+.class_size =
Am 31.01.2014 12:42, schrieb Paolo Bonzini:
Il 30/01/2014 20:48, Eduardo Habkost ha scritto:
There isn't any kind of registration involved in cpu_x86_register()
anymore: it is simply looking up a CPU model name and loading the model
definition data into the X86CPU object. Rename it to
Am 30.01.2014 20:48, schrieb Eduardo Habkost:
As we will initialize the X86CPU fields on instance_init eventually,
move the code that initializes the X86CPU data based on the CPU model
name closer to the object_new() call.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Thanks, applied
Am 31.01.2014 12:42, schrieb Paolo Bonzini:
Il 30/01/2014 20:48, Eduardo Habkost ha scritto:
As the new X86CPU subclass code is going to change lots of the code
invoving x86_def_t, let's rename the struct to match coding style first.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
[...]
shorter and easier to review.
Later we can gradually convert each X86CPUDefinition field to lists of
per-class property defaults.
Written based on the ideas from the patch [RFC v5] target-i386: Slim
conversion to X86CPU subclasses + KVM subclasses written by Andreas
Färber afaer...@suse.de
Am 06.02.2014 17:16, schrieb Eduardo Habkost:
(CCing libvir-list again, as this is continuing a discussion about a
subject that interests libvirt developers, from another thread.)
On Thu, Feb 06, 2014 at 04:51:17PM +0100, Andreas Färber wrote:
Am 06.02.2014 16:19, schrieb Igor Mammedov
Am 30.01.2014 22:47, schrieb Paolo Bonzini:
Il 30/01/2014 20:48, Eduardo Habkost ha scritto:
Is there any hope to get this into QEMU 2.0, or it is now too late? I got
almost no feedback on take 6 (submitted November 27).
It's not too late, not for me at least. I wanted to send the next
Am 21.01.2014 10:51, schrieb Chen Fan:
On Tue, 2014-01-21 at 10:31 +0100, Igor Mammedov wrote:
On Tue, 21 Jan 2014 15:12:45 +0800
Chen Fan chen.fan.f...@cn.fujitsu.com wrote:
On Mon, 2014-01-20 at 13:29 +0100, Igor Mammedov wrote:
On Fri, 17 Jan 2014 17:13:55 -0200
Eduardo Habkost
Am 22.08.2013 18:12, schrieb Eduardo Habkost:
On 22/08/2013, at 12:39, Andrew Jones drjo...@redhat.com wrote:
The comment in kvm_max_vcpus() states that it's using the recommended
procedure from the kernel API documentation to get the max number
of vcpus that kvm supports. It is, but by
Am 21.08.2013 19:02, schrieb Paolo Bonzini:
Il 21/08/2013 19:03, Michael S. Tsirkin ha scritto:
It is a source of pain, and the previous patch anyway changed the
behavior of -M pc-1.5 compared to the real 1.5.
This also makes it clear that -device pvpanic is not enough:
it will not expose
Am 21.08.2013 19:01, schrieb Michael S. Tsirkin:
On Wed, Aug 21, 2013 at 06:43:16PM +0200, Paolo Bonzini wrote:
The pvpanic situation is already messed up enough. Let us give our
libvirt friends an easy indication that we have untied our side.
Not-yet-signed-off-by: Paolo Bonzini
Am 09.08.2013 17:58, schrieb Anthony Liguori:
Even if we had an algorithm for calculating memory overhead (we don't),
glibc will still introduce uncertainty since malloc(size) doesn't
translate to allocating size bytes from the kernel. When you throw in
fragmentation too it becomes extremely
Am 05.08.2013 09:40, schrieb Laine Stump:
On 08/04/2013 07:55 PM, Doug Goldstein wrote:
On Sat, Aug 3, 2013 at 9:01 PM, Laine Stump la...@laine.org wrote:
q35 machines have an implicit ahci (sata) controller at 00:1F.2 which
has no id associated with it. For this reason, we can't refer to it
Am 25.07.2013 20:02, schrieb Eduardo Habkost:
On Thu, Jul 25, 2013 at 04:09:18PM +0200, Andreas Färber wrote:
Am 25.07.2013 16:00, schrieb Eduardo Habkost:
libvirt
needs a way to find out how exactly -machine foo-1.0 -cpu bar looks
different from -machine foo-1.1 -cpu bar,
Why? (What's
Am 24.07.2013 20:25, schrieb Eduardo Habkost:
In addition to the -cpu host KVM initialization problem, this is an
additional problem with the current interfaces provided by QEMU:
1) libvirt needs to query data that depend on chosen machine-type and
CPU model
2) Some machine-type behavior
Am 25.07.2013 16:00, schrieb Eduardo Habkost:
libvirt
needs a way to find out how exactly -machine foo-1.0 -cpu bar looks
different from -machine foo-1.1 -cpu bar,
Why? (What's the actual use case?)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,
Am 25.05.2013 11:18, schrieb Peter Maydell:
On 24 May 2013 22:38, Eric Blake ebl...@redhat.com wrote:
I think knowing the architecture (such as x86 vs. pseries ppc) is used
by libvirt to know what default devices the board supports (for example,
whether usb is present by default).
...but
Am 03.05.2013 17:54, schrieb Eduardo Habkost:
On Fri, May 03, 2013 at 05:16:46PM +0200, Andreas Färber wrote:
Am 22.04.2013 21:00, schrieb Eduardo Habkost:
FEAT_7_0_EBX uses ECX as input, so we have to take that into account
when reporting feature word values.
Signed-off-by: Eduardo Habkost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.05.2013 17:01, schrieb Eric Blake:
On 04/22/2013 01:00 PM, Eduardo Habkost wrote:
Instead of open-coding the filtering code for each feature word,
change the existing code to use the feature_word_info array, that
have exactly the same CPUID
Am 06.05.2013 18:20, schrieb Eduardo Habkost:
Resubmitting after a rebase and a few trivial changes.
Changes v11 - v12:
* Remove unnecessary entries from .gitignore
* Fix indentation of x86_cpu_get_feature_words() declaration
* Rebase on top of qom-cpu-next
(commit bd87d2a -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 02.05.2013 21:48, schrieb Eric Blake:
On 05/02/2013 01:43 PM, Eduardo Habkost wrote:
As mentioned earlier I'd prefer to defer the property design
rather than putting it lightly reviewed into 1.5 and living
with some ABI. If libvirt urgently
Am 22.04.2013 21:00, schrieb Eduardo Habkost:
FEAT_7_0_EBX uses ECX as input, so we have to take that into account
when reporting feature word values.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
target-i386/cpu.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
Am 22.04.2013 21:00, schrieb Eduardo Habkost:
This series includes the previous replace cpuid_*features fields with a
feature
word array series.
The first 4 patches already have a Reviewed-by from Igor, they correspond to
v10
plus a small indent fix requested by him.
As the
Am 22.04.2013 21:00, schrieb Eduardo Habkost:
Add appropriate spaces around operators, and break line where it needs
to be broken to allow feature-words array to be introduced without
having too-long lines.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Reviewed-By: Igor Mammedov
Am 22.04.2013 21:00, schrieb Eduardo Habkost:
This replaces the feature-bit fields on both X86CPU and x86_def_t
structs with an array.
With this, we will be able to simplify code that simply does the same
operation on all feature words (e.g. kvm_check_features_against_host(),
:
- Emit an empty event on unnamed devices in patch 1/3, as suggested by
Markus
Changes from v4:
- Add extra triggers and extra fields as requested by Markus
Series looks good,
Reviewed-by: Andreas Färber afaer...@suse.de
Andreas
Changes from v3:
- Document that we only
from v2:
- move event toward the end of device_unparent,
so that parents are reported after their children,
as suggested by Paolo
Changes from v1:
- move to device_unparent
- address comments by Andreas and Eric
Reviewed-by: Andreas Färber afaer...@suse.de
Thanks
Am 01.03.2013 14:12, schrieb Jiri Denemark:
On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote:
= Listing CPU models =
Requirement: libvirt needs to know which CPU models are available to be used
with the -cpu option.
Current problem: libvirt relies on help output parsing for
Am 21.02.2013 21:57, schrieb Eduardo Habkost:
On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
Eduardo Habkost ehabk...@redhat.com writes:
This allows , to be used a separator between each CPU range. Note
that commas inside key=value command-line options have to be escaped
Am 15.01.2013 17:16, schrieb Juan Quintela:
* cpu hot plug
- use qdev propierties conected to a set of socket objects (anthony)
- cpusets are the wrong interface (anthony)
- make a link between cpu - socket instead of a propierty?
- how far are we from being able to describe a cpu
Am 30.01.2013 13:49, schrieb Eduardo Habkost:
On Wed, Jan 30, 2013 at 11:58:56AM +0100, Andreas Färber wrote:
* CPU class_init for -cpu host requires KVM init (imammedo)
[suggestion by ehabkost to use kvm_arch_vcpu_init, WIP by afaerber]
I don't know what you mean by use kvm_arch_vcpu_init
Am 07.01.2013 19:20, schrieb Eduardo Habkost:
KVM_CAP_PV_MMU capability reporting was removed from the kernel since
v2.6.33 (see commit a68a6a7282373), and was completely removed from the
kernel since v3.3 (see commit fb92045843). It doesn't make sense to keep
it enabled by default, as it
Am 07.01.2013 19:20, schrieb Eduardo Habkost:
Feature names were taken from the X86_FEATURE_* constants in the Linux
kernel code.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
Cc: Gleb Natapov g...@redhat.com
---
target-i386/cpu.c | 17 +
1 file changed, 17
Am 07.01.2013 19:20, schrieb Eduardo Habkost:
Eduardo Habkost (7):
kvm: Add fake KVM constants to avoid #ifdefs on KVM-specific code
[...]
target-i386: Disable kvm_mmu by default
target-i386/cpu: Introduce FeatureWord typedefs
target-i386: kvm_check_features_against_host(): Use
Am 04.01.2013 23:01, schrieb Eduardo Habkost:
Eduardo Habkost (11):
[...]
target-i386: kvm: -cpu host: Use GET_SUPPORTED_CPUID for SVM features
target-i386: kvm: Enable all supported KVM features for -cpu host
target-i386: check/enforce: Fix CPUID leaf numbers on error messages
Am 26.07.2012 15:53, schrieb Eduardo Habkost:
On Wed, Jul 25, 2012 at 06:43:25PM -0500, Anthony Liguori wrote:
Eduardo Habkost ehabk...@redhat.com writes:
Hi,
This is the first try at a simple system to make the CPU model definitions
versioned (to allow them to get bug fixes while allowing
Am 26.07.2012 16:24, schrieb Eduardo Habkost:
On Thu, Jul 26, 2012 at 12:52:33AM +0200, Andreas Färber wrote:
Am 25.07.2012 20:18, schrieb Eduardo Habkost:
This adds version number to CPU model names on the pc-version
machine-types, so we can create new models with bug fixes while keeping
Am 25.07.2012 20:18, schrieb Eduardo Habkost:
This allow QEMUMachine structs to contain a list of CPU model aliases,
used to keep command-line compatibility with older machine types, while
making CPU model fixes available on newer machine types.
Signed-off-by: Eduardo Habkost
Am 25.07.2012 20:18, schrieb Eduardo Habkost:
This adds version number to CPU model names on the pc-version
machine-types, so we can create new models with bug fixes while keeping
compatibility when using older machine-types.
When naming the existing models, I used the last QEMU version
Am 08.06.2012 09:44, schrieb Anthony Liguori:
On 06/08/2012 03:11 PM, Andreas Färber wrote:
Am 08.06.2012 03:22, schrieb Anthony Liguori:
On 06/08/2012 03:31 AM, Andreas Färber wrote:
From: Paolo Bonzinipbonz...@redhat.com
Some classes may present objects differently in errors, for example
Am 02.05.2012 18:07, schrieb Eduardo Habkost:
Changes v2 - v3:
- Rebase against latest qemu.git
Changes v1 - v2:
- Change 'userconfig' field/variables to bool instead of int
- Coding style change
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
arch_init.c | 11
Am 28.05.2012 08:35, schrieb Paolo Bonzini:
Il 27/05/2012 16:02, Andreas Färber ha scritto:
Any suggestion how to fix?
Sorry, I forgot to reply here that I've sent a patch.
Does it work to typedef _Bool __bool before including altivec.h (and
in the same #ifdef)?
Haven't tried but I'm afraid
Am 02.05.2012 15:50, schrieb Eduardo Habkost:
Anthony, isn't this going to get in for 1.1? I was expecting it to be
applied before the freeze.
You wrote you would respin it with s/int/bool/. :)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,
Commit 4a19f1eced611e7c3a0fba07d13515cbc73da09f (r7036) added a
configure option --with-pkgversion for distributions and forks to label
their derived versions.
bsd-user was not updated at the time, so fix this while at it.
Signed-off-by: Andreas Färber afaer...@suse.de
---
bsd-user/main.c
since it has been sensitive to changes there in the past.
Regards,
Andreas
Cc: Anthony Liguori anth...@codemonkey.ws
Cc: Fabrice Bellard fabr...@bellard.org
Cc: Peter Maydell peter.mayd...@linaro.org
Cc: Natalia Portillo clau...@claunia.com
Cc: libvirt libvir-list@redhat.com
Andreas Färber (2
just changing the year seems wrong since Fabrice didn't
contribute in recent years. Therefore extend the copyright statement to
cover Fabrice Bellard and contributors so that it can be updated
to the current year.
Cc: Fabrice Bellard fabr...@bellard.org
Signed-off-by: Andreas Färber afaer
Am 11.03.2012 17:16, schrieb Gleb Natapov:
On Sun, Mar 11, 2012 at 10:33:15AM -0500, Anthony Liguori wrote:
On 03/11/2012 09:56 AM, Gleb Natapov wrote:
On Sun, Mar 11, 2012 at 09:12:58AM -0500, Anthony Liguori wrote:
-cpu best wouldn't solve this. You need a read/write configuration
file
Am 10.03.2012 19:24, schrieb Anthony Liguori:
Humans probably do one of two things: 1) no cpu option or 2) -cpu host.
So then why are you introducing -cpu Westmere?
[...]
P.S. I spent 30 minutes the other day helping a user who was attempting
to figure out whether his processor was a Conroe,
Am 12.03.2012 17:50, schrieb Eduardo Habkost:
On Mon, Mar 12, 2012 at 04:49:47PM +0100, Andreas Färber wrote:
Am 11.03.2012 17:16, schrieb Gleb Natapov:
On Sun, Mar 11, 2012 at 10:33:15AM -0500, Anthony Liguori wrote:
On 03/11/2012 09:56 AM, Gleb Natapov wrote:
On Sun, Mar 11, 2012 at 09:12
Am 12.03.2012 18:47, schrieb Peter Maydell:
On 12 March 2012 17:41, Andreas Färber afaer...@suse.de wrote:
Also keep in mind linux-user. There's no concept of a machine there, but
there's a cpu_copy() function used for forking that tries to re-create
the CPU based on its model.
Incidentally
60 matches
Mail list logo
