Signed-off-by: zhanghailiang
---
qga/commands-posix.c | 7 +++
qga/commands-win32.c | 6 ++
qga/qapi-schema.json | 26 ++
3 files changed, 39 insertions(+)
diff --git a/qga/commands-posix.c b/qga/commands-posix.c
index f6f3e3c..b4d5c29 100644
--- a/qga/commands-
Hi,
This patch series add a new guest command 'guest-get-os-version'.
It is now only available for windows guest.
It will return guest's OS version name and type, like bellow:
'{"return":{"name":"Microsoft Windows Server 2012 R2","type":64}}'
Sometimes we need to know guest's OS version info.
(A
We can get guest's OS version info by using 'guest-get-os-version',
The return value contains version name and type (32-bit or 64-bit).
For example:
{"return":{"name":"Microsoft Windows Server 2012 R2","type":64}}
Signed-off-by: zhanghailiang
---
qga/commands-win32.c | 123 ++
On Mo, 2014-12-15 at 15:37 +, Peter Maydell wrote:
> On 15 December 2014 at 09:23, Gerd Hoffmann wrote:
>
> >> > Does anybody know how this is supposed to work? Is the fix as
> >> > simple as just moving the free_resources call below the fini?
> >
> > I suspect the code simply wasn't written
On (Tue) 16 Dec 2014 [16:38:15], David Gibson wrote:
> On Tue, Dec 16, 2014 at 10:08:49AM +0530, Amit Shah wrote:
> > On (Tue) 16 Dec 2014 [15:33:54], David Gibson wrote:
> > > On Tue, Dec 16, 2014 at 09:43:30AM +0530, Amit Shah wrote:
> > > > Can you split this patch so the config change and the
On 2014/12/9 18:29, Eric Auger wrote:
> This new C module will be used by ARM machine files to generate
> platform bus node and their dynamic sysbus device tree nodes.
>
> Dynamic sysbus device node addition is done in a machine init
> done notifier. arm_register_platform_bus_fdt_creator does the
On Tue, Dec 16, 2014 at 10:08:49AM +0530, Amit Shah wrote:
> On (Tue) 16 Dec 2014 [15:33:54], David Gibson wrote:
> > On Tue, Dec 16, 2014 at 09:43:30AM +0530, Amit Shah wrote:
> > > On (Fri) 12 Dec 2014 [16:26:35], David Gibson wrote:
> > > > On a bi-endian target, with a guest in the non-default
On Wed, Dec 10, 2014 at 12:46 AM, Alistair Francis wrote:
> This patch adds the stm32f2xx USART controller
> (UART also uses the same controller).
>
> Signed-off-by: Alistair Francis
> ---
> V6:
> - Rename to STM32F2XX
> - Fix up unimplemented printing
> - Add a qemu_chr_accept()
> V3:
> - Up
On 2014/12/9 18:29, Eric Auger wrote:
> Allows sysbus devices to be instantiated from command line by
> using -device option. Machvirt creates a platform bus at init.
> The dynamic sysbus devices are attached to this platform bus device.
>
> The platform bus device registers a machine init done no
On Wed, Dec 10, 2014 at 12:46 AM, Alistair Francis wrote:
> This patch adds the stm32f2xx timers: TIM2, TIM3, TIM4 and TIM5
> to QEMU.
>
> Signed-off-by: Alistair Francis
> ---
> V6:
> - Rename to STM32F2XX
> - Change the timer calculations to use ns
> - Update the value to timer_mod to ensure
On (Tue) 16 Dec 2014 [15:33:54], David Gibson wrote:
> On Tue, Dec 16, 2014 at 09:43:30AM +0530, Amit Shah wrote:
> > On (Fri) 12 Dec 2014 [16:26:35], David Gibson wrote:
> > > On a bi-endian target, with a guest in the non-default endian mode,
> > > attempting to migrate twice in a row with a virt
On Tue, Dec 16, 2014 at 09:43:30AM +0530, Amit Shah wrote:
> On (Fri) 12 Dec 2014 [16:26:35], David Gibson wrote:
> > On a bi-endian target, with a guest in the non-default endian mode,
> > attempting to migrate twice in a row with a virtio-serial device wil
> > cause a qemu SEGV on the second outg
On (Fri) 12 Dec 2014 [16:26:35], David Gibson wrote:
> On a bi-endian target, with a guest in the non-default endian mode,
> attempting to migrate twice in a row with a virtio-serial device wil
> cause a qemu SEGV on the second outgoing migration.
>
> The problem is that virtio_serial_save_device(
The patch implements sPAPRPHBClass::eeh_handler so that the
EEH RTAS requests can be routed to VFIO for further handling.
Signed-off-by: Gavin Shan
---
hw/misc/vfio.c | 1 +
hw/ppc/spapr_pci_vfio.c | 56 +
2 files changed, 57 insertions(+
The emulation for EEH RTAS requests from guest isn't covered
by QEMU yet and the patch implements them.
The patch defines constants used by EEH RTAS calls and adds
callback sPAPRPHBClass::eeh_handler, which is going to be used
this way:
* RTAS calls are received in spapr_pci.c, sanity check is
The series of patches adds support EEH for VFIO PCI devices on sPAPR platform.
It requires corresponding host kernel support, which was merged during 3.17
merge window. This patchset has been rebased to Alex Graf's QEMU repository:
git://github.com/agraf/qemu.git (branch: ppc-next)
The impleme
From: Alexey Kardashevskiy
This makes find_phb()/find_dev() public and changed its names
to spapr_pci_find_phb()/spapr_pci_find_dev() as they are going to
be used from other parts of QEMU such as VFIO DDW (dynamic DMA window)
or VFIO PCI error injection or VFIO EEH handling - in all these
cases t
Ping!
在 12/12/2014 05:53 PM, Yang Hongyang 写道:
Only free qsb that qemu_bufopen allocated, and also allow
qemu_bufopen accept qsb as input for write operation. It
will make the API more logical:
1.If you create the QEMUSizedBuffer yourself, you need to
free it by using qsb_free() but not depen
On Tue, Dec 16, 2014 at 01:59:01AM +0100, Alexander Graf wrote:
>
>
> On 16.12.14 01:43, David Gibson wrote:
> > At the moment the RTAS (firmware/hypervisor) time of day functions are
> > implemented in spapr_rtas.c along with a bunch of other things. Since
> > we're going to be expanding these
On Tue, Dec 16, 2014 at 02:04:49AM +0100, Alexander Graf wrote:
>
>
> On 16.12.14 01:43, David Gibson wrote:
> > On x86, the guest's RTC can be read with QMP via the "rtc-time" property
> > on the /machine object. This is due to an explicit QOM alias being set up
> > by the mc146818rtc driver, a
On Tue, Dec 16, 2014 at 02:01:29AM +0100, Alexander Graf wrote:
>
>
> On 16.12.14 01:43, David Gibson wrote:
> > The virtual RTC time is used in two places in the pseries machine. First
> > is in the RTAS get-time-of-day function which returns the RTC time to the
> > guest. Second is in the spa
On Thu, 12/04 11:43, Fam Zheng wrote:
> v2: Emulate nanoseconds precison of timeout with ppoll and timerfd.
> Their performance is on par with each other, but both much better than
> qemu.git:
>
> syscall high # of fd low # of fd
> -
--
Thanks,
Yang.
It's been a while, but ping^3
As it's only an RFC I haven't bothered re-basing it, I can if anyone
wants it rebased.
Thanks,
Alistair
On Fri, Jun 27, 2014 at 12:58 AM, Peter Maydell
wrote:
> On 26 June 2014 06:09, Alistair Francis wrote:
>> Ping^2
>
> Hi. This is still on my must-review queue
Signed-off-by: Fam Zheng
---
qapi/block-core.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 6e8db15..2d8bd25 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -423,7 +423,7 @@
# @device: #optional If the st
On Mon, Dec 15, 2014 at 03:59:56PM +0100, Alexander Graf wrote:
>
>
> On 12.12.14 06:26, David Gibson wrote:
> > On a bi-endian target, with a guest in the non-default endian mode,
> > attempting to migrate twice in a row with a virtio-serial device wil
> > cause a qemu SEGV on the second outgoin
On 16.12.14 01:43, David Gibson wrote:
> On x86, the guest's RTC can be read with QMP via the "rtc-time" property
> on the /machine object. This is due to an explicit QOM alias being set up
> by the mc146818rtc driver, and doesn't work on other targets.
>
> This extends the pseries RTAS RTC to
On 16.12.14 01:43, David Gibson wrote:
> The virtual RTC time is used in two places in the pseries machine. First
> is in the RTAS get-time-of-day function which returns the RTC time to the
> guest. Second is in the spapr events code which is used to timestamp
> event messages from the hypervis
On 16.12.14 01:43, David Gibson wrote:
> At the moment the RTAS (firmware/hypervisor) time of day functions are
> implemented in spapr_rtas.c along with a bunch of other things. Since
> we're going to be expanding these a bit, move the RTAS RTC related code
> out into new file spapr_rtc.c. Also
On Thu, 11/27 12:40, Vladimir Sementsov-Ogievskiy wrote:
> Mirror and migration use dirty bitmaps for their purposes, and since
> commit [block: per caller dirty bitmap] they use their own bitmaps, not
> the global one. But they use old functions bdrv_set_dirty and
> bdrv_reset_dirty, which change
On 16.12.14 01:31, Gavin Shan wrote:
> On Tue, Dec 16, 2014 at 01:08:52AM +0100, Alexander Graf wrote:
>>
>>
>> On 16.12.14 00:29, Gavin Shan wrote:
>>> On Tue, Dec 16, 2014 at 12:13:03AM +0100, Alexander Graf wrote:
On 16.12.14 00:08, Gavin Shan wrote:
> On Mon, Dec 15, 2014 at 03:52:17
Currently, the RTAS time of day functions only partially validate the
number of parameters they receive and return. Because of how the
parameters are used, this is unlikely to lead to a crash, but it's messy.
This patch adds the missing checks.
Signed-off-by: David Gibson
---
hw/ppc/spapr_rtc.
At the moment, the PAPR RTC implementation (actually a paravirt
firmware interface, rather than a normal device) works directly off
host time, and so doesn't respect the options such as clock=vm which
can be specified in the -rtc command line option.
This patch addresses this also making some othe
On x86, the guest's RTC can be read with QMP via the "rtc-time" property
on the /machine object. This is due to an explicit QOM alias being set up
by the mc146818rtc driver, and doesn't work on other targets.
This extends the pseries RTAS RTC to populate that property, for improved
management com
At the moment the RTAS (firmware/hypervisor) time of day functions are
implemented in spapr_rtas.c along with a bunch of other things. Since
we're going to be expanding these a bit, move the RTAS RTC related code
out into new file spapr_rtc.c. Also add its own initialization function,
spapr_rtc_i
In the 'pseries' machine the real time clock is provided by a
paravirtualized firmware interface rather than a device per se; the RTAS
get-time-of-day and set-time-of-day calls.
Out current implementations of those work directly off host time (with
an offset), not respecting options such as clock=
The virtual RTC time is used in two places in the pseries machine. First
is in the RTAS get-time-of-day function which returns the RTC time to the
guest. Second is in the spapr events code which is used to timestamp
event messages from the hypervisor to the guest.
Currently both call qemu_get_ti
On Tue, Dec 16, 2014 at 01:08:52AM +0100, Alexander Graf wrote:
>
>
>On 16.12.14 00:29, Gavin Shan wrote:
>> On Tue, Dec 16, 2014 at 12:13:03AM +0100, Alexander Graf wrote:
>>> On 16.12.14 00:08, Gavin Shan wrote:
On Mon, Dec 15, 2014 at 03:52:17PM +0100, Alexander Graf wrote:
> On 15.12.1
On 16.12.14 00:29, Gavin Shan wrote:
> On Tue, Dec 16, 2014 at 12:13:03AM +0100, Alexander Graf wrote:
>> On 16.12.14 00:08, Gavin Shan wrote:
>>> On Mon, Dec 15, 2014 at 03:52:17PM +0100, Alexander Graf wrote:
On 15.12.14 01:15, Gavin Shan wrote:
> The emulation for EEH RTAS requests fr
Paolo Bonzini writes:
Something like this?
diff --git a/target-s390x/mem_helper.c b/target-s390x/mem_helper.c
index 5a55de8..4de3fc2 100644
--- a/target-s390x/mem_helper.c
+++ b/target-s390x/mem_helper.c
@@ -490,10 +490,18 @@ uint32_t HELPER(ex)(CPUS390XState *env, uint32_t cc,
On Tue, Dec 16, 2014 at 12:13:03AM +0100, Alexander Graf wrote:
>On 16.12.14 00:08, Gavin Shan wrote:
>> On Mon, Dec 15, 2014 at 03:52:17PM +0100, Alexander Graf wrote:
>>> On 15.12.14 01:15, Gavin Shan wrote:
The emulation for EEH RTAS requests from guest isn't covered
by QEMU yet and th
From: Fabian Aggeler
Set ARM_FEATURE_EL3 feature for CPUs that implement Security Extensions.
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
target-arm/cpu.c | 4
1 file changed, 4 insertions(+)
diff --git a/target-arm/cpu.c b/target-arm/cpu.c
Adds setting of the CPU has_el3 property based on the vexpress machine
secure state property during initialization. This enables/disables EL3
state during start-up. Changes include adding an additional secure state
boolean during vexpress CPU initialization. Also enables the ARM secure boot
by d
Adds setting of the CPU has_el3 property based on the virt machine
secure state property during initialization. This enables/disables EL3
state during start-up. Changes include adding an additional secure state
boolean during virt CPU initialization. Also disables the ARM secure boot
by default.
Disables the CPU ARM_FEATURE_EL3 featuere on machine models that can be
configured to use Cortex-A9, Cortex-A15, and ARM1176 but don't officially
support EL3. This preserves backwards compatibility.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw/arm/exynos4210.c | 11 +
On 16.12.14 00:08, Gavin Shan wrote:
> On Mon, Dec 15, 2014 at 03:52:17PM +0100, Alexander Graf wrote:
>> On 15.12.14 01:15, Gavin Shan wrote:
>>> The emulation for EEH RTAS requests from guest isn't covered
>>> by QEMU yet and the patch implements them.
>>>
>>> The patch defines constants used b
Added a "has_el3" state property to the ARMCPU descriptor. This property
indicates whether the ARMCPU has security extensions enabled (EL3) or not.
By default it is disabled at this time.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
v1 -> v2
- Added set of has_el3 to true when E
Add "secure" virt machine specific property to allow override of the
default secure state configuration. By default, when using the QEMU
-kernel command line argument, virt machines boot into NS/SVC. When using
the QEMU -bios command line argument, virt machines boot into S/SVC.
The secure state
Adds the secure_boot boolean field to the arm_boot_info descriptor. This
fields is used to indicate whether Linux should boot into secure or non-secure
state if the ARM EL3 feature is enabled. The default is to leave the CPU in an
unaltered reset state. On EL3 enabled systems, the reset state is
This commit changes the integratorcp and versatilepb CPU initialization from
using the generic ARM cpu_arm_init function to doing it inline. This is
necessary in order to allow CPU configuration changes to occur between CPU
instance initialization and realization. Specifically, this change is in
Switch virt qemu machine support to use the newer object type, class, and
instance model. Added virt TypeInfo with static registration along with virt
specific class and machine structs. Also added virt class initialization
method.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw
Add an unset_feature() function to compliment the set_feature() function. This
will be used to disable functions after they have been enabled during
initialization.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
target-arm/cpu.c | 5 +
1 file changed, 5 insertions(+)
diff --gi
Add "secure" Vexpress machine specific property to allow override of the
default secure state configuration. By default, when using the QEMU
-kernel command line argument, Vexpress machines boot into NS/SVC. When using
the QEMU -bios command line argument, Vexpress machines boot into S/SVC.
The
Add Vexpress machine objects for the the Cortex A9 & A15 variants. The older
style QEMUMachine types were replaced with dedicated TypeInfo objects. The new
objects include dedicated class init functions that currently ustilze dedicated
machine init methods. The previous qemu_register_machine call
Change the Vexpress daughterboard initialization method to take a vexpress
machine state pointer instead of the daughterboard struct pointer. The machine
state now contains the daughterboard pointer.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw/arm/vexpress.c | 10 +-
Switched the Vexpress machine initialization to use the common function with
the machine pointer to board info.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw/arm/vexpress.c | 26 --
1 file changed, 4 insertions(+), 22 deletions(-)
diff --git a/hw/arm/vex
This patchset adds functionality for enabling the ARM CPU security extensions.
At this time, the only machines supported are Versatile Express and the QEMU
ARM virtual machines both with Cortex A9 & A15.
The patchset establishes the default security state along with adding
overriding controls of t
Adds base Vexpress class and machine objects and infrastructure. This is in
preparation for switching to the full QEMU object model. The base vexpress
infrastructure is intended to handle common vexpress details.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
v1 -> v2
- Made the
On Mon, Dec 15, 2014 at 03:52:17PM +0100, Alexander Graf wrote:
>On 15.12.14 01:15, Gavin Shan wrote:
>> The emulation for EEH RTAS requests from guest isn't covered
>> by QEMU yet and the patch implements them.
>>
>> The patch defines constants used by EEH RTAS calls and adds
>> callback sPAPRPHB
I'm trying to track down some CPU usage issues we're having with some
virtual machines. Basically, when we run our application under KVM, we
see about 2x the CPU usage that we would see if we were running it on
bare metal.
kvm_stat shows me the following:
efer_reload 0
On 15 December 2014 at 21:45, Greg Bellows wrote:
> Should the has_el3 property errors on these machines also be silent (will
> break -cpu host).
All the ones in this patch use the
if (object_property_find(OBJECT(cpu), "has_el3", NULL)) {
object_property_set_bool(OBJECT(cpu), false,
Should the has_el3 property errors on these machines also be silent (will
break -cpu host).
Greg
On 15 December 2014 at 11:09, Peter Maydell
wrote:
>
> On 11 December 2014 at 23:29, Greg Bellows
> wrote:
> > Disables the CPU ARM_FEATURE_EL3 featuere on machine models that can be
> > configured
On 11/12/2014 14:55, Peter Lieven wrote:
> On 02.12.2014 12:05, Paolo Bonzini wrote:
>> As discussed in the other thread, this brings speedups from
>> dropping the coroutine mutex (which serializes multiple iothreads,
>> too) and using ELF thread-local storage.
>>
>> The speedup in perf/cost is a
On 12/15/2014 03:11 PM, Paolo Bonzini wrote:
>
> On 12/12/2014 20:15, miny...@acm.org wrote:
>> +if (s->threaded_bmc) {
>> +qemu_mutex_init(&s->lock);
>> +qemu_cond_init(&s->waker);
>> +qemu_thread_create(&s->thread, "ipmi-bmc", ipmi_thread, s, 0);
>> +}
>> +
>> +
On 12/15/2014 05:20 PM, Daniel P. Berrange wrote:
On Mon, Dec 15, 2014 at 04:16:02PM +0100, Alexander Graf wrote:
On 10.12.14 14:19, Marcel Apfelbaum wrote:
The help is based on the actual machine properties
exposing only the relevant options.
Signed-off-by: Marcel Apfelbaum
Can libvirt ma
On 12/12/2014 20:15, miny...@acm.org wrote:
> This set of patches adds an IPMI device to qemu. This is good for
> systems that require an IPMI device to work correctly, for simulating
> scenarios that require IPMI and testing software that uses IPMI, and
> of course, for the Linux IPMI driver ma
On 12/12/2014 20:15, miny...@acm.org wrote:
> +if (s->threaded_bmc) {
> +qemu_mutex_init(&s->lock);
> +qemu_cond_init(&s->waker);
> +qemu_thread_create(&s->thread, "ipmi-bmc", ipmi_thread, s, 0);
> +}
> +
> +if (s->threaded_bmc) {
> +qemu_mutex_init(&s-
For the record, the workaround is deleting old snapshots in shutdown mode
as per comment #14.
Upstream has moved toward external snapshots as the way forward, so while
I don't argue that this is a bug, it seems unlikely to receive a fix from
upstream.
--
You received this bug notification becaus
EMU:
Confirmed
Bug description:
From a run of cppcheck, a static analysis checker, over the
source code of qemu trunk, dated 20141215, is the new error:
[qemu/target-tricore/translate.c:3812]: (style) Expression '(X & 0x3f)
== 0x6f' is always false.
Source code is
The mask is actually 7 bit long, instead of 6, so the expression checking
for JNZ.T is always false. Let's make the mask 1 bit wider.
Signed-off-by: Bastian Koppelmann
---
target-tricore/translate.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-tricore/translate.
QEMU:
Confirmed
Bug description:
From a run of cppcheck, a static analysis checker, over the
source code of qemu trunk, dated 20141215, is the new error:
[qemu/target-tricore/translate.c:3812]: (style) Expression '(X & 0x3f)
== 0x6f' is always false.
Source cod
** Changed in: qemu (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
Stat
On 15 December 2014 at 13:43, Peter Maydell
wrote:
>
> On 15 December 2014 at 18:51, Greg Bellows
> wrote:
> > Add "secure" Vexpress machine specific property to allow override of the
> > default secure state configuration. By default, when using the QEMU
> > -kernel command line argument, Vexpr
@michael, so you do that once, after some time the machine keeps
growing, and growing and growing... and you have to redo that every so
often... I have a machine that should be taking up 30 gb yet is taking
600+ GB with 4 snapshots... but yeah... I'll just plug in another 1tb
hard drive so that i
On 15 December 2014 at 18:51, Greg Bellows wrote:
> -object_property_set_description(obj, "secure",
> - "Set on/off to enable/disable secure state",
> - NULL);
> +object_property_set_description(obj, "secure", SECURE_PROP_DESC, NULL);
Same r
On 15 December 2014 at 18:51, Greg Bellows wrote:
> Adds setting of the CPU has_el3 property based on the vexpress machine
> secure state property during initialization. This enables/disables EL3
> state during start-up. Changes include adding an additional secure state
> boolean during vexpress
On 15 December 2014 at 18:51, Greg Bellows wrote:
> Adds the secure_boot boolean field to the arm_boot_info descriptor. This
> fields is used to indicate whether Linux should boot into secure or non-secure
> state if the ARM EL3 feature is enabled. The default is to leave the CPU in
> an
> unal
On 15 December 2014 at 18:51, Greg Bellows wrote:
> Added a "has_el3" state property to the ARMCPU descriptor. This property
> indicates whether the ARMCPU has security extensions enabled (EL3) or not.
> By default it is disabled at this time.
>
> Signed-off-by: Greg Bellows
Reviewed-by: Peter
On 15 December 2014 at 18:51, Greg Bellows wrote:
> Add "secure" virt machine specific property to allow override of the
> default secure state configuration. By default, when using the QEMU
> -kernel command line argument, virt machines boot into NS/SVC. When using
> the QEMU -bios command line
On 15 December 2014 at 18:51, Greg Bellows wrote:
> Add "secure" Vexpress machine specific property to allow override of the
> default secure state configuration. By default, when using the QEMU
> -kernel command line argument, Vexpress machines boot into NS/SVC. When using
> the QEMU -bios comm
Public bug reported:
>From a run of cppcheck, a static analysis checker, over the
source code of qemu trunk, dated 20141215, is the new error:
[qemu/target-tricore/translate.c:3812]: (style) Expression '(X & 0x3f)
== 0x6f' is always false.
Source code is
if (unl
On 11/27/2014 04:40 AM, Vladimir Sementsov-Ogievskiy wrote:
Mirror and migration use dirty bitmaps for their purposes, and since
commit [block: per caller dirty bitmap] they use their own bitmaps, not
the global one. But they use old functions bdrv_set_dirty and
bdrv_reset_dirty, which change a
From: Fabian Aggeler
Set ARM_FEATURE_EL3 feature for CPUs that implement Security Extensions.
Signed-off-by: Fabian Aggeler
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
target-arm/cpu.c | 4
1 file changed, 4 insertions(+)
diff --git a/target-arm/cpu.c b/target-arm/cpu.c
Switch virt qemu machine support to use the newer object type, class, and
instance model. Added virt TypeInfo with static registration along with virt
specific class and machine structs. Also added virt class initialization
method.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw
Disables the CPU ARM_FEATURE_EL3 featuere on machine models that can be
configured to use Cortex-A9, Cortex-A15, and ARM1176 but don't officially
support EL3. This preserves backwards compatibility.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw/arm/exynos4210.c | 11 +
Adds the secure_boot boolean field to the arm_boot_info descriptor. This
fields is used to indicate whether Linux should boot into secure or non-secure
state if the ARM EL3 feature is enabled. The default is to leave the CPU in an
unaltered reset state. On EL3 enabled systems, the reset state is
This commit changes the integratorcp and versatilepb CPU initialization from
using the generic ARM cpu_arm_init function to doing it inline. This is
necessary in order to allow CPU configuration changes to occur between CPU
instance initialization and realization. Specifically, this change is in
Add "secure" Vexpress machine specific property to allow override of the
default secure state configuration. By default, when using the QEMU
-kernel command line argument, Vexpress machines boot into NS/SVC. When using
the QEMU -bios command line argument, Vexpress machines boot into S/SVC.
The
Adds setting of the CPU has_el3 property based on the virt machine
secure state property during initialization. This enables/disables EL3
state during start-up. Changes include adding an additional secure state
boolean during virt CPU initialization. Also disables the ARM secure boot
by default.
Added a "has_el3" state property to the ARMCPU descriptor. This property
indicates whether the ARMCPU has security extensions enabled (EL3) or not.
By default it is disabled at this time.
Signed-off-by: Greg Bellows
---
v1 -> v2
- Added set of has_el3 to true when EL3 is enabled
v2 -> v3
- Pr
Adds setting of the CPU has_el3 property based on the vexpress machine
secure state property during initialization. This enables/disables EL3
state during start-up. Changes include adding an additional secure state
boolean during vexpress CPU initialization. Also enables the ARM secure boot
by d
Switched the Vexpress machine initialization to use the common function with
the machine pointer to board info.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw/arm/vexpress.c | 26 --
1 file changed, 4 insertions(+), 22 deletions(-)
diff --git a/hw/arm/vex
Add an unset_feature() function to compliment the set_feature() function. This
will be used to disable functions after they have been enabled during
initialization.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
target-arm/cpu.c | 5 +
1 file changed, 5 insertions(+)
diff --gi
Add "secure" virt machine specific property to allow override of the
default secure state configuration. By default, when using the QEMU
-kernel command line argument, virt machines boot into NS/SVC. When using
the QEMU -bios command line argument, virt machines boot into S/SVC.
The secure state
Adds base Vexpress class and machine objects and infrastructure. This is in
preparation for switching to the full QEMU object model. The base vexpress
infrastructure is intended to handle common vexpress details.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
v1 -> v2
- Made the
Add Vexpress machine objects for the the Cortex A9 & A15 variants. The older
style QEMUMachine types were replaced with dedicated TypeInfo objects. The new
objects include dedicated class init functions that currently ustilze dedicated
machine init methods. The previous qemu_register_machine call
Change the Vexpress daughterboard initialization method to take a vexpress
machine state pointer instead of the daughterboard struct pointer. The machine
state now contains the daughterboard pointer.
Signed-off-by: Greg Bellows
Reviewed-by: Peter Maydell
---
hw/arm/vexpress.c | 10 +-
This patchset adds functionality for enabling the ARM CPU security extensions.
At this time, the only machines supported are Versatile Express and the QEMU
ARM virtual machines both with Cortex A9 & A15.
The patchset establishes the default security state along with adding
overriding controls of t
Signed-off-by: Eduardo Habkost
---
tests/test-x86-cpu.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/tests/test-x86-cpu.c b/tests/test-x86-cpu.c
index b6e4382..fb3de05 100644
--- a/tests/test-x86-cpu.c
+++ b/tests/test-x86-cpu.c
@@ -54,6 +54,30 @@ static void tes
The unit test includes target-i386/cpu.c instead of simply linking
against cpu.o because the test code will use static variables/functions
from cpu.c.
Reasoning for each object file included in the test binary:
* qom/cpu.o - for TYPE_CPU. Dependencies:
* qom/qom-qobject.o
* qom/qdev.o - for T
1 - 100 of 352 matches
Mail list logo
