by me i was
able to bring up vhost-net on 32-bit ARM.
Is there any work still needed on this ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Hello!
thanks for your inputs. I think both series are up-to-date wrt last
comments.
So is it going to be included in the next release ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
index 97a1fb0..a86c816 100644
--- a/hw/virtio/virtio-mmio.c
+++ b/hw/virtio/virtio-mmio.c
@@ -22,6
checks
kvm_eventfds_enabled() for this purpose, so backwards compatibility is much
better.
I confirm that this solution significantly improves the network performance
even without using irqfd.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Same as host notifier of virtio-mmio, most of codes came from virtio-pci.
The kvm-arm does not yet support irqfd, need to fix the hard-coded part
after
kvm-arm gets irqfd support.
Signed-off-by: Ying-Shiuan Pan address@hidden
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio
Signed-off-by: Ying-Shiuan Pan address@hidden
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 47
++-
1 file changed, 46 insertions(+), 1 deletion(-)
diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
index
set_host_notifier() is introduced into virtio-mmio now. Most of codes came
from virtio-pci.
Signed-off-by: Ying-Shiuan Pan address@hidden
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 70
+
1 file changed, 70
,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
where it is stuck is after initializing usbcore. After hitting
enter it says switching clocksource to... (i don't remember) and goes on.
After this it can stop like this again, in some random moment.
Which kernel version do you use for guest ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung
know any implementation of
aarch64 except A57 and A53 (which are the same from software point of view).
So, i believe, A57 is quite a reasonable default.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
set_host_notifier() is introduced into virtio-mmio now. Most of codes came
from virtio-pci.
Signed-off-by: Ying-Shiuan Pan address@hidden
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 72
+
1 file changed, 72
Same as host notifier of virtio-mmio, most of codes came from virtio-pci.
The kvm-arm does not yet support irqfd, need to fix the hard-coded part
after
kvm-arm gets irqfd support.
Signed-off-by: Ying-Shiuan Pan address@hidden
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio
Signed-off-by: Ying-Shiuan Pan address@hidden
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 47
+++
1 file changed, 47 insertions(+)
diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
index 8756240..0ab270d
: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
--- сut ---
So far, i think the GICv3 functionality is OK. Here is my line.
Tested-by: Pavel Fedin p.fe
mode.
But, sorry, i will unlikely implement this, because we already have PCI with
MSI-X (i
hope this is going to be published soon), so my project can use PCI emulation.
So
implementing irqfds for virtio-mmio is a bit out of my scope.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics
of fantasy.
I have tested the implementation with kernel v4.1rc2 and 16 CPUs. Works
perfectly fine,
no lockups were observed.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm/virt.c | 145 --
1 file changed, 120 insertions(+), 25
. Shouldn't our default for virt be just host ? This
would eliminate all ambiguity i believe...
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
arguments.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
unfortunately don't have time for further refactor. If you ACK, i will resend
the series
once again as v3, i set up git send-email and it should be working now.
I just wanted to share this piece because it's already done, and i would not
like it to
go to oblivion again.
Kind regards,
Pavel Fedin
Hello!
I'm afraid this is wrong -- the same command line on qemu-system-arm and
qemu-system-aarch64 should do the same thing.
But 64-bit A15 is nonsense, because it's 32-bit CPU, isn't it?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
as int in order to be
architecture agnostic,
for potential future users.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm/virt.c | 155 +++-
include/hw/boards.h | 1 +
2 files changed, 130 insertions(+), 26 deletions(-)
diff --git
This small patch fixes a long-standing bug: A15 model is used by default
also on ARM64 target. As a result, attempt to run the VM without explicit
-cpu specification does not do anything good.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm/virt.c | 4
1 file changed, 4
to
the original message in which the patch was published, with comments and
tested-by: tag ? In this case, how can i, if i don't have this message in my
email client (subscribed after that) ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Hello!
This is updated version of my eventfd for virtio-mmio patch. Style notes
have been considered, hopefully it's OK now.
It's now 3 parts instead of 4, because the last one was actually a small
fix, i decided to merge it with no 3.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung
. In v1 series cover letter
i wrote about that, just for v2 i decided not to retype the whole intro.
Perhaps that was a bad idea.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
).
My current guest kernel is v3.19.5. I will test on 4.1rc2 soon.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 61 +
1 file changed, 61 insertions(+)
diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
index da56b9c..a4c4d89 100644
--- a/hw/virtio/virtio-mmio.c
+++ b/hw/virtio/virtio
From: Ying-Shiuan Pan yingshiuan@gmail.com
Signed-off-by: Ying-Shiuan Pan yingshiuan@gmail.com
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 47 +++
1 file changed, 47 insertions(+)
diff --git a/hw/virtio/virtio
From: Ying-Shiuan Pan yingshiuan@gmail.com
set_host_notifier() is introduced into virtio-mmio now. Most of codes came
from virtio-pci.
Signed-off-by: Ying-Shiuan Pan yingshiuan@gmail.com
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/virtio/virtio-mmio.c | 73
This patch set introduces eventfd support for virio-mmio. It was originally
published by Ying-Shiuan Pan but never got it to upstream:
https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg00715.html
I have updated and successfully tested it with vhost-net. I confirm that this
solution
-devel/2015-05/msg01304.html, so feel
free to
re-add it back.
BTW, just for interest, have you tried to do anything with KVM support of
vGICv3? I have
some code but it's inherently unstable and lock up for unknown (yet) reason.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics
be missing
from the
patch.
But, may be something has changed in master over the last three days? Actually
my base
tree is from friday.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
, if we don't have in-kernel acceleration, perhaps the good idea is stick
to what the user wants, and use emulation. Yes, i know about problems with
generic timer in this case, but this if different issue which can also be fixed.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research
And one more small note... I have noticed a typo.
--- cut ---
[VIRT_ITS_CONTROL] = { 0x0802, 0x1000 },
--- cut ---
The size should actually be 0x0001. It worked because we don't use ITS.
Please fix it
for the next merge attempt.
Kind regards,
Pavel Fedin
Expert Engineer
://lists.gnu.org/archive/html/qemu-devel/2015-05/msg01505.html
I added Shlomo to cc because he might also be interested.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Hello! I have published v3 3 days ago, and got no single reply. Was it lost?
I've
(hopefully) done everything you asked for, and sent it using git send-email
from the
command line. So should work.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
it running. I believe it's interpretation
mode flaw.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
perfectly OK with any name change. I just
decided that v3 would stand for GICv3. If you have such a policy, let it
be. No objections.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
, Create kernel irqchip failed\n);
return ret;
}
}
--- cut ---
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
? Is it intentional or not?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
in qmp_check_input_obj() function should be brought
back
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
This fixes QMP regression:
http://lists.gnu.org/archive/html/qemu-devel/2015-06/msg01795.html
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
monitor.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/monitor.c b/monitor.c
index c7baa91..ef21bba 100644
--- a/monitor.c
+++ b/monitor.c
Hi!
I think that Pavel's needs to address all the issues in the original thread.
Ok. I have read the thread and i'll prepare a fixed version of this shortly.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
would it be acceptable to leave mpidr handling as it is?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
function which needs
full version is mpidr_read(). So does it still worth of putting AND with
bitmasks everywhere? May be just rename 'mpidr' to something like 'mp_id' ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
-off-by: Pavel Fedin p.fe...@samsung.com
---
Changes since v3:
1. Fixed and/or updated comments and descriptions
2. CPUS_PER_CLUSTER replaced by a variable which can be changed by machine
initialization
code
3. PSCI looks up processor directly by ID, no more ID-index conversion
4. Added ID fixup
as well like it is done in
ARM for
mpidr, but it
has been decoupled form it, converted to property and
set by board code now which is topology aware.
Can you point at the code? I'm not familiar with x86 stuff.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
.
The property is a uint32_t and has the original name of the array ('name[*]')
for simplicity. It has getter function in order to allow to inspect it from
within monitor.
The modification decreases qemu startup time with 32 CPUs by a factor of 2
(~10 sec vs ~20 sec).
Signed-off-by: Pavel Fedin p.fe
Hello Luiz! Have you missed this ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
-Original Message-
From: qemu-devel-bounces+p.fedin=samsung@nongnu.org [mailto:qemu-devel-
bounces+p.fedin=samsung@nongnu.org] On Behalf Of Pavel Fedin
Hello! More than week ago i've done this patch but it seems to be lost. It is
a part of
my vGICv3 project and i decided to post it separately because vGICv3 code
itself waits for
Shlomo's patches.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
properties start only from qdev class. I decided not to write too much
code for a single use case. It's even slightly faster to use a pointer. And by
design this property is supposed to be read-only, because anyway setting it
from outside isn't a good idea.
Kind regards,
Pavel Fedin
Expert Engineer
is better than no progress. But it's just IMHO. So, OK, if you
think it has to wait, it can wait.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
, it does. I feed unmodified tree to the qemu and the model successfully
boots up. On another machine, with working vGIC, the same kernel and DTB
correctly recognizes architected timer.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
RaspberryPi 2, as far as i know. Also i am testing on some Samsung
proprietary HW which has the same problem.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Hello!
Also some boards have no fallback timer device at all (notably
virt, so generic-timer *has* to work.
Yes, some boards indeed don't have it. And virt, indeed, doesn't work. But, at
least i can run vexpress guest.
I'm out of further arguments. :)
Kind regards,
Pavel Fedin
Expert
Useful for removing devices from the tree
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
device_tree.c| 10 ++
include/sysemu/device_tree.h | 10 ++
2 files changed, 20 insertions(+)
diff --git a/device_tree.c b/device_tree.c
index d2de580..f666df4 100644
with machine models which actually have these
timers (like vexpress).
Pavel Fedin (2):
Introduce qemu_fdt_remove_compatible()
Remove CP15 timer from the device tree if KVM is used without
in-kernel irqchip
device_tree.c| 10 ++
hw/arm/boot.c| 5
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm/boot.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index 1e7fd28..35a2aa2 100644
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -10,6 +10,7 @@
#include config.h
#include hw/hw.h
#include hw/arm
Hello!
I see only affinity patch went in. What is the status of the rest of GICv3
stuff?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
.
The property is a uint32_t and has the original name of the array ('name[*]')
for simplicity. It has getter function in order to allow to inspect it from
within monitor.
The modification decreases qemu startup time with 32 CPUs by a factor of 2
(~10 sec vs ~20 sec).
Signed-off-by: Pavel Fedin
implementation is waiting. It even
has support for proposed in-kernel ITS emulation:
http://www.mail-archive.com/kvm@vger.kernel.org/msg116057.html
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
MPIDR values, and fail if not.)
I believe this is a different story.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
(), to avoid this
What is better?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
not seem to have such thing as bus number,
therefore we
use only devfn. This is OK for platforms with only one PCI bus instance. Perhaps
additional property should be implemented when we emulate some GICv3-based
machine with
more than one bus.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/pci
beyond #7 will
not power up in KVM.
And when are you planning to post v3? I am waiting for it to be integrated, in
order to
add KVM vGICv3. Otherwise i'm afraid there are too many collisions.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
it is possible to do it in reverse and assign MPIDR to VCPUs
using
KVM_SET_ONE_REG ioctl instead. I can try it if you think it's more appropriate.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
the code which cares about it (PSCI and Shlomo's GICv3
software
emulation) is not used with KVM. So i think we have no other choice if we want
to be
compatible with current KVM APIs.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
is pending until
your patch
series is
integrated?
Just make it a part of your V3. I'm perfectly OK with that. Looks like
maintainers don't
want to integrate it alone.
I intend to release the V3 version during this week.
Good.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics
on ARM-Linux mailing list, and
qemu
support will rely on this (it will have to pass CONTROL region to KVM and
intercept
TRANSLATION region).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
GICv3 ITS distinguishes between devices by using hardwired device IDs passed on
the bus.
This patch implements passing these IDs in qemu.
SMMU is also known to use stream IDs, therefore this addition can also be
useful for
implementing platforms with SMMU.
Signed-off-by: Pavel Fedin p.fe
it's ready for application, but my
message
seems to have been lost. Looks like i forgot Cc to the maintainer. My current
vGICv3
work-in-progress is based on this.
If Shlomo does not respond until friday, i think i'll post a new vGICv3 series
based on
master.
Kind regards,
Pavel Fedin
Expert
accepts IDs set by qemu, but in this case
we would
have inconsistency between device tree and real IDs. And there seems to be no
way round.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
once and not every time for every property (there
can be
thousands of them)
The modification decreases qemu startup time with 32 ARMv8 CPUs by a factor of
2 (~10 sec
vs ~20 sec).
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
qom/object.c | 89
people time to do the respin or other things.
I am giving it. A week has passed. Actually one of goals of my project here at
Samsung is
to upstream our changes, that's why i worry about it.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
to be
changed. But you could set it from inside virt before instantiating CPUs if you
want to
change it.
When CPUs are instantiated their IDs will be auto-generated from index (raw
order number)
according to this parameter.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center
* going through. I studied APIC
code, looks
like they encode all the stuff into MSI data.
Does this mean that qemu currently lacks support for device identifiers in MSI
?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
the
ITS control
ITS
translation.
ITS memory regions is another thing, it is in virt machine definition.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
.
The first patch from the mentioned series is already in master; Peter told me
that he doesn't want
to add the complete GICv3 before qemu 2.4 is released:
https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg04171.html
So waiting...
Kind regards,
Pavel Fedin
Expert Engineer
Samsung
series have stalled somehow, and I would
like to see what we can do to get this stuff moving again.
For this purpose you can talk to Peter i guess, because it was his decision.
By the way, when does
freeze period end?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center
Ping!
May be you could PULL it? Andreas seems to be down...
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
property by itself.
up to the use of [*] for the
new property iiuc.
What would you suggest instead? Personally i don't have much preferences, i
used it just because it was already there.
What about 'name#' ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center
Instantiate kvm-arm-gicv3 class for GICv3 with KVM acceleration
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm/virt.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
index 5c07d07..100cb17 100644
--- a/hw/arm/virt.c
+++ b/hw/arm
From: Shlomo Pongratz shlomo.pongr...@huawei.com
Implement GIC-500 from GICv3 family for arm64
This patch is a first step toward 128 cores support for arm64.
At first only 64 cores are supported for two reasons:
First the largest integer type has the size of 64 bits and modifying
essential data
helper routines are
used instead.
- Put informative commit messages
Pavel Fedin (6):
Add virt-v3 machine that uses GIC-500
Extract some reusable vGIC code
Set kernel_irqchip_type for the rest of ARM boards which use GIC
Make use of kernel_irqchip_type in kvm_arch_irqchip_create()
Initial
be again tedious (either ugly casts or qemu-style
separate object pointer). So i disliked it too.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/intc/arm_gic_kvm.c | 84 ---
hw/intc/vgic_common.h | 43 ++
2 files changed, 82
by now.
If you really dislike it, you can simply leave parts 2 and 3 out, because the
rest (KVM vGICv3) does not depend on it in any way. I included it only in order
to provide the complete solution.
Shlomo? Your turn...
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research
software GIC emulation. Everyone okay with this? Peter?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Just in case, the value is set for absolutely all board models which include
GIC in some form. I am not sure whether all these models can use KVM
acceleration, but it definitely would not hurt.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm/exynos4_boards.c | 1 +
hw/arm/realview.c
This function is actually used only for capability verification, but now it
will check for the correct GIC type.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
include/sysemu/kvm.h | 3 ++-
kvm-all.c| 2 +-
stubs/kvm.c | 2 +-
target-arm/kvm.c | 8 ++--
4 files
), and then
check user-supplied value against GIC limitation by myself. And produce error.
This will be code duplication. Do you think it is better?
Anybody else (Peter, Cristoffer ?), please vote.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Get/put routines are missing, live migration is not possible.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/intc/Makefile.objs | 1 +
hw/intc/arm_gicv3_kvm.c | 203
2 files changed, 204 insertions(+)
create mode 100644 hw/intc
From: Shlomo Pongratz shlomo.pongr...@huawei.com
This class is to be used by both software and KVM implementations of GICv3
Signed-off-by: Shlomo Pongratz shlomo.pongr...@huawei.com
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/intc/Makefile.objs | 1 +
hw/intc
From: Shlomo Pongratz shlomo.pongr...@huawei.com
Add system instructions used by the Linux (kernel) GICv3
device driver
Signed-off-by: Shlomo Pongratz shlomo.pongr...@huawei.com
---
target-arm/cpu.h | 12 ++
target-arm/cpu64.c | 105 +
.
Currently it it used only by virt machine for its internal purposes, however in
future it is to be passed to KVM in kvm_irqchip_create(). The variable is
defined as int in order to be architecture agnostic, for potential future
users.
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/arm
without LPIs). So yes, i'll split it up a bit more.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
work here, doesn't this automatically mean that he is
sharing it with the community? Additionally, i do not drop his authorship.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
From: Shlomo Pongratz shlomo.pongr...@huawei.com
This class is to be used by both software and KVM implementations of GICv3
Signed-off-by: Shlomo Pongratz shlomo.pongr...@huawei.com
Signed-off-by: Pavel Fedin p.fe...@samsung.com
---
hw/intc/Makefile.objs | 1 +
hw/intc
1 - 100 of 511 matches
Mail list logo
