, I heard the scream on IRC. Sorry.
;-)
Acked-by: Matt Evans m...@ozlabs.org
Matt
--
To unsubscribe from this list: send the line unsubscribe kvm-ppc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
By enable, I mean fix; the re-jigged commit 7ef85e8b builds libfdt
using OBJS rather than OTHEROBJS hence ignores the relaxed CFLAGS.
This commit builds it via OTHEROBJS.
Signed-off-by: Matt Evans m...@ozlabs.org
---
Pekka, not quite sure how this slipped through as I was building static
On 31 Jan 2012, at 18:59, Pekka Enberg wrote:
On Tue, Jan 31, 2012 at 8:34 AM, Matt Evans m...@ozlabs.org wrote:
+static struct cpu_info cpu_power7_info = {
+ POWER7,
+ power7_page_sizes_prop, sizeof(power7_page_sizes_prop),
+ power7_segment_sizes_prop, sizeof
On 31 Jan 2012, at 19:11, Pekka Enberg wrote:
On Tue, Jan 31, 2012 at 8:34 AM, Matt Evans m...@ozlabs.org wrote:
+#define DEBUG_SPAPR_HCALLS
I suppose this shouldn't be defined by default?
Well, I had a bit of a debate about it. I left it on as it is actually
interesting whilst
SPAPR support includes various in-kernel hypercalls, improving performance
by cutting out the exit to userspace. H_BULK_REMOVE is implemented in this
patch.
Signed-off-by: Matt Evans m...@ozlabs.org
---
Alex, my zomg, ls SIGILLs! on IRC was due to a former broken version of
this patch
dependency on 64bit libfdt (which isn't in some
distros).
- Spit polish
Thanks to David Alex for the PPC-related reviews!
Matt Evans (7):
kvm tools: PPC64, add HPT/SDR1 for -PR KVM
kvm tools: Generate SPAPR PPC64 guest device tree
kvm tools: Add SPAPR PPC64 hcall rtascall structure
forced to use them.
A new option, '--hugetlbfs default', uses a default path for 16M pages for
HV mode, if required.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/powerpc/include/kvm/kvm-arch.h |2 ++
tools/kvm/powerpc/kvm-cpu.c | 24 +---
tools/kvm
and PPC970 host CPUs.
Future support of more CPUs is possible.
libfdt is included from scripts/dtc/libfdt.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile | 26 -
tools/kvm/powerpc/cpu_info.c | 83
tools/kvm/powerpc
This adds the console code, plus VIO HV terminal nodes are added to
the device tree so the guest kernel will pick it up.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |1 +
tools/kvm/powerpc/kvm.c | 33
tools/kvm/powerpc/spapr_hvcons.c
This is the final piece of the puzzle for PPC SPAPR PCI; this
function splits MMIO accesses into the two PHB windows directs
things to MMIO/IO emulation as appropriate.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |1 +
tools/kvm/powerpc/include
This provides the PCI bridge, definitions for the address layout of the windows
and wires in IRQs. Once PCI devices are all registered, they are enumerated and
DT nodes generated for each.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/powerpc/include/kvm/kvm-arch.h |3 +
tools/kvm
Hey Alex,
On 24/12/11 00:39, Alexander Graf wrote:
On 23.12.2011, at 14:26, Matt Evans wrote:
On 23/12/2011, at 11:58 PM, Alexander Graf wrote:
On 13.12.2011, at 07:21, Matt Evans wrote:
Different architectures will deal with MMIO exits differently. For
example,
KVM_EXIT_IO is x86
Heya Alex,
On 13/12/11 19:23, Alexander Graf wrote:
On 13.12.2011, at 08:00, Matt Evans m...@ozlabs.org wrote:
This patch adds a new arch directory, powerpc, basic file structure, register
setup and where necessary stubs out arch-specific functions (e.g. interrupts,
runloop exits
On 15/12/11 12:37, Alexander Graf wrote:
On 15.12.2011, at 02:27, Matt Evans wrote:
Heya Alex,
On 13/12/11 19:23, Alexander Graf wrote:
On 13.12.2011, at 08:00, Matt Evans m...@ozlabs.org wrote:
This patch adds a new arch directory, powerpc, basic file structure,
register
setup
On 14 Dec 2011, at 04:43, Pekka Enberg penb...@kernel.org wrote:
On Tue, Dec 13, 2011 at 9:00 AM, Matt Evans m...@ozlabs.org wrote:
+int irq__register_device(u32 dev, u8 *num, u8 *pin, u8 *line)
+{
+ fprintf(stderr, irq__register_device(%d, [%d], [%d], [%d]\n,
+ dev
On 13/12/11 21:23, Sasha Levin wrote:
On Tue, 2011-12-13 at 18:00 +1100, Matt Evans wrote:
The second patch is a small fix for generic virtio code (now that we have a
PPC build) which removes reliance on ioeventfds for PPC, which doesn't
provide
them.
Hm... ioeventfds are located
The last remaining patches from the preparation series, with changes:
- Map from hugetlbfs does plain statfs (without odd error checking),
checks result of ftruncate()
- Remove typo whereby kvm_cpu__emulate_mmio() calls self.
Cheers,
Matt
Matt Evans (2):
kvm tools: Add ability to map
MADV_HUGEPAGES so that, if the user asks for hugepages, we definitely
are using hugepages. (This is particularly useful for architectures that
don't yet support KVM without hugepages, so we definitely need to use
them for the whole of guest RAM.)
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools
the main runloop's IO and MMIO exit handlers. For x86, these directly
call kvm__emulate_io() and kvm__emulate_mmio() but other architectures will
perform some address munging before passing on the call.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm-cpu.c | 34
Hi Pekka,
On 09/12/11 17:53, Matt Evans wrote:
kvmtool's types.h includes asm/types.h, which by default on PPC64 brings in
int-l64.h; define __SANE_USERSPACE_TYPES__ to get LL64 types.
This patch also adds CFLAGS to the final link, so that any -m64 is obeyed
when linking, too.
Just noticed
provide
them.
Matt Evans (2):
kvm tools: Add initial SPAPR PPC64 architecture support
kvm tools: Make virtio-pci's ioeventfd__add_event() fall back
gracefully if ioeventfds unavailable
tools/kvm/Makefile | 10 +
tools/kvm/include/kvm/ioeventfd.h|3
(plus initrd).
(bzImages are not used on PPC, and this series does not add zImage support or an
ELF loader.) The intention is to later support loading firmware such as SLOF.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile | 10 +
tools/kvm/kvm.c
Some KVM implementations (e.g. PPC) don't yet support ioeventfds, so don't
bomb out/die. virtio-pci is able to function if it instead uses normal IO
port notification.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile|2 +-
tools/kvm/include/kvm/ioeventfd.h
of the code within is borrowed/based upon code in QEMU, particularly
the XICS emulation, device tree construction and PCI setup.
Matt Evans (6):
kvm tools: Generate SPAPR PPC64 guest device tree
kvm tools: Add SPAPR PPC64 hcall rtascall structure
kvm tools: Add SPAPR PPC64 HV console
kvm
of a variety
of POWER CPUs should acquire this info from the host and encode appropriately.
This requires a 64-bit libfdt.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |3 +-
tools/kvm/powerpc/include/kvm/kvm-arch.h | 10 ++
tools/kvm/powerpc/kvm.c
tree.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |2 +
tools/kvm/powerpc/kvm-cpu.c |6 +
tools/kvm/powerpc/kvm.c | 46 -
tools/kvm/powerpc/spapr.h | 105 ++
tools/kvm/powerpc/spapr_hcall.c | 132
This is the final piece of the puzzle for PPC SPAPR PCI; this
function splits MMIO accesses into the two PHB windows directs
things to MMIO/IO emulation as appropriate.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |1 +
tools/kvm/powerpc/include
On 09/12/11 19:29, Pekka Enberg wrote:
On Fri, Dec 9, 2011 at 10:24 AM, Sasha Levin levinsasha...@gmail.com wrote:
If you also got kernel patches that add __SANE_USERSPACE_TYPES__ to the
headers, and KVM_CAP_NR_VCPUS to KVM PPC, we can carry them in the KVM
tools tree as well.
Yup, all we
On 09/12/11 18:39, Sasha Levin wrote:
On Fri, 2011-12-09 at 17:55 +1100, Matt Evans wrote:
Add a --hugetlbfs commandline option to give a path to hugetlbfs-map guest
memory (down in kvm__arch_init()). For x86, guest memory is a normal
ANON mmap() if this option is not provided, otherwise
on top of Pekka's linux-kvm.git as of today.
Cheers,
Matt
Matt Evans (23):
kvm tools: Only build/init i8042 on x86
kvm tools: Add Makefile parameter for kernel include path
kvm tools: Re-arrange Makefile to heed CFLAGS before checking for
optional libs
kvm tools: Get correct 64-bit
Not every architecture has an i8042 kbd controller, so only use this when
building for x86.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |2 +-
tools/kvm/builtin-run.c |2 ++
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/Makefile b
The checks for optional libraries build code to perform the tests, so should
respect certain CFLAGS -- in particular, -m64 so we check for 64bit libraries if
they're required.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile | 86
This patch adds an 'I' parameter to override the default kernel include path of
'../../include'.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/Makefile b/tools/kvm/Makefile
index f58a1d8
kvmtool's types.h includes asm/types.h, which by default on PPC64 brings in
int-l64.h; define __SANE_USERSPACE_TYPES__ to get LL64 types.
This patch also adds CFLAGS to the final link, so that any -m64 is obeyed
when linking, too.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile
This patch creates a new function in x86/kvm-cpu.c, kvm_cpu__handle_exit(), in
which arch-specific exit reasons can be handled outside of the common runloop.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/kvm-cpu.h |2 ++
tools/kvm/kvm-cpu.c | 10
We die() if we can't read KVM_CAP_NR_VCPUS, but the API docs suggest to assume
the value 4 in this case. This is pertinent to PPC KVM, which currently
does not support this CAP.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c |6 +-
1 files changed, 5 insertions(+), 1
Different systems will want different base kernel commandlines, e.g. non-x86
systems probably don't need noapic, i8042.* etc., so set the commandline up in
arch-specific code. Then, if the resulting commandline is empty, don't strcat a
space onto the front.
Signed-off-by: Matt Evans m
kvm_cpu__run() currently die()s if KVM_RUN returns non-zero. Some architectures
may return positive values in non-error cases, whereas real errors are always
negative return values. Check for those instead.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm-cpu.c |2 +-
1 files
This patch paves the way for adding a hypervisor console, useful on systems that
support one out of the box yet don't have either serial port or virtio console
support (e.g. kernels expecting POWER SPAPR).
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |8
cpios are valid as initrds too, so allow them through the check.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c
index 0bbe9ba..d26e3d7 100644
--- a/tools/kvm/kvm.c
architecture. :-)
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/kvm.h |2 +-
tools/kvm/kvm.c | 10 ++
tools/kvm/x86/kvm.c | 13 ++---
3 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/tools/kvm/include/kvm/kvm.h b/tools
Re-arrange pci__init() in builtin-run such that it comes before devices are
initialised.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index
Add a --hugetlbfs commandline option to give a path to hugetlbfs-map guest
memory (down in kvm__arch_init()). For x86, guest memory is a normal
ANON mmap() if this option is not provided, otherwise a hugetlbfs mmap.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c
vesa, pci-shmem and virtio-pci devices need to set up config space with
little-endian conversions (as config space is LE). The pci_config_address
bitfield also needs to be reversed when building on BE systems.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/hw/pci-shmem.c | 23
pci_get_io_space_block() used to grab addresses from
KVM_32BIT_GAP_START + 0x100, which is x86-specific. Create a new define,
KVM_PCI_MMIO_AREA, to specify a bus address these allocations can come from.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/pci.c
PPC KVM lacks these two capabilities, and as such a userland system must assume
a max of 4 VCPUs (following api.txt). With these, a userland can determine
a more realistic limit.
Signed-off-by: Matt Evans m...@ozlabs.org
---
Alex: For when you're back in civilisation -- the kvmtool/PPC stuff
;) )
Cheers,
Matt
On Tue, 2011-12-06 at 14:39 +1100, Matt Evans wrote:
kvm_cpu__run() currently die()s if KVM_RUN returns non-zero. Some
architectures
may return positive values in non-error cases, whereas real errors are always
negative return values. Check for those instead.
Signed-off
On 08/12/11 15:49, Ingo Molnar wrote:
* Matt Evans m...@ozlabs.org wrote:
On 08/12/11 04:14, Pekka Enberg wrote:
On Wed, 7 Dec 2011, Ingo Molnar wrote:
* Matt Evans m...@ozlabs.org wrote:
[...] I haven't looked closely at Matt's
patches, but it should be possible to use [un]signed
On 08/12/11 15:56, Matt Evans wrote:
On 08/12/11 15:49, Ingo Molnar wrote:
* Matt Evans m...@ozlabs.org wrote:
On 08/12/11 04:14, Pekka Enberg wrote:
On Wed, 7 Dec 2011, Ingo Molnar wrote:
* Matt Evans m...@ozlabs.org wrote:
[...] I haven't looked closely at Matt's
patches
On 08/12/11 16:49, Ingo Molnar wrote:
* Matt Evans m...@ozlabs.org wrote:
Since tools/kvm/include/linux/types.h only requires __u32,
__u64 et al from asm/types.h, wouldn't it be most
straightforward to just #include asm-generic/int-ll64.h?
This avoids #define __KERNEL__ breaking other
to the expanded the return codes (and updating api.txt) for
varying kinds of positive success?
Cheers,
Matt
On Tue, 2011-12-06 at 14:39 +1100, Matt Evans wrote:
kvm_cpu__run() currently die()s if KVM_RUN returns non-zero. Some
architectures
may return positive values in non-error cases
initial SPAPR PPC64 architecture support patch, which uses it. I could've
mushed that into the later PPC series but I thought it'd be clearer to do the
generic/x86 stuff separately.
Matt
On Tue, 2011-12-06 at 14:41 +1100, Matt Evans wrote:
Some architectures may want to use hugetlbfs to mmap
Hi Cyrill,
On 06/12/11 23:04, Cyrill Gorcunov wrote:
On Tue, Dec 06, 2011 at 12:29:48PM +0200, Pekka Enberg wrote:
...
Otherwise looks OK to me. Cyrill?
It might be not seen from patch (or my local kvm repo
is not yet updated well) but I somehow miss who will be
reading initrd in case
Hi Asias,
On 06/12/11 23:00, Asias He wrote:
On 12/06/2011 06:24 PM, Pekka Enberg wrote:
On Tue, Dec 6, 2011 at 5:40 AM, Matt Evans m...@ozlabs.org wrote:
term_getc()'s int c has one byte written into it (at its lowest address) by
read_in_full(). This is expected to be the least significant
this patch from the series. ;-)
Thanks,
Matt
On Tue, 2011-12-06 at 14:41 +1100, Matt Evans wrote:
CONFIG_HAS_BFD is optional, symbol.c inclusion is optional -- so make its
init
call dependent on CONFIG_HAS_BFD.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c
to 4 CPUs until the kernel
supports that CAP. (I'll see about this part too.)
Thanks,
Matt
On Tue, 2011-12-06 at 14:39 +1100, Matt Evans wrote:
Architectures can recommend/count/determine number of CPUs differently, so
move
this out of generic code.
Signed-off-by: Matt Evans m
.
Cheers,
Matt
On Tue, 2011-12-06 at 14:43 +1100, Matt Evans wrote:
Different architectures will deal with MMIO exits differently. For example,
KVM_EXIT_IO is x86-specific, and I/O cycles are often synthesisted by
steering
into windows in PCI bridges on other architectures
Hi Ingo,
On 06/12/11 21:24, Ingo Molnar wrote:
* Paul Mackerras pau...@samba.org wrote:
On Tue, Dec 06, 2011 at 09:28:27AM +0100, Ingo Molnar wrote:
* Sasha Levin levinsasha...@gmail.com wrote:
Ingo actually got us to remove all the PRI* specifiers, but
that was back when we only did
On 07/12/11 17:34, Sasha Levin wrote:
On Wed, 2011-12-07 at 17:17 +1100, Matt Evans wrote:
On 06/12/11 19:20, Sasha Levin wrote:
Why is it getting moved out of generic code?
This is used to determine the maximum amount of vcpus supported by the
host for a single guest, and as far as I know
On 07/12/11 05:59, Scott Wood wrote:
On 12/05/2011 09:37 PM, Matt Evans wrote:
Not every architecture has an i8042 kbd controller, so only use this when
building for x86.
There are non-x86 machines that have one, though -- does KVM tool have
any sort of target configuration mechanism?
See
Not every architecture has an i8042 kbd controller, so only use this when
building for x86.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |2 +-
tools/kvm/builtin-run.c |2 ++
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/Makefile b
This patch adds an 'I' parameter to override the default kernel include path of
'../../include'.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/Makefile b/tools/kvm/Makefile
index f58a1d8
Architectures can recommend/count/determine number of CPUs differently, so move
this out of generic code.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c | 30 --
tools/kvm/x86/kvm.c | 30 ++
2 files changed, 30
kvm_cpu__run() currently die()s if KVM_RUN returns non-zero. Some architectures
may return positive values in non-error cases, whereas real errors are always
negative return values. Check for those instead.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm-cpu.c |2 +-
1 files
Currently, the SIGALRM handler calls device poll functions (for serial, virtio
console) directly. Which devices are present and which require polling is a
system-specific decision, so create a new function called from common code
move the x86-specific poll calls into it.
Signed-off-by: Matt
Fix a missing include.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c
index e526483..33243f1 100644
--- a/tools/kvm/kvm.c
+++ b/tools/kvm/kvm.c
@@ -8,6 +8,7 @@
#include
Different systems will want different base kernel commandlines, e.g. non-x86
systems probably don't need noapic, i8042.* etc., so set the commandline up in
arch-specific code. Then, if the resulting commandline is empty, don't strcat a
space onto the front.
Signed-off-by: Matt Evans m
This patch paves the way for adding a hypervisor console, useful on systems that
support one out of the box yet don't have either serial port or virtio console
support (e.g. kernels expecting POWER SPAPR).
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |8
than an int.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/term.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/tools/kvm/term.c b/tools/kvm/term.c
index fb5d71c..440884e 100644
--- a/tools/kvm/term.c
+++ b/tools/kvm/term.c
@@ -30,11 +30,10 @@ int term_fds
cpios are valid as initrds too, so allow them through the check.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c
index 33243f1..457de1a 100644
--- a/tools/kvm/kvm.c
CONFIG_HAS_BFD is optional, symbol.c inclusion is optional -- so make its init
call dependent on CONFIG_HAS_BFD.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm
architecture. :-)
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/kvm.h |2 +-
tools/kvm/kvm.c | 10 ++
tools/kvm/x86/kvm.c | 12 +---
3 files changed, 16 insertions(+), 8 deletions(-)
diff --git a/tools/kvm/include/kvm/kvm.h b/tools
Re-arrange pci__init() in builtin-run such that it comes before devices are
initialised.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index
setup, cpu init
to occur last.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c | 24 ++--
1 files changed, 14 insertions(+), 10 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index 32e19e7..576dcfa 100644
--- a/tools/kvm/builtin
Some architectures may want to use hugetlbfs to mmap() their guest memory, so
allow a path to be specified on the commandline and pass it to kvm__arch_init().
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |4 +++-
tools/kvm/include/kvm/kvm.h |4 ++--
tools/kvm
Other pieces of kvmtool may be interested in PCI_MAX_DEVICES.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/pci.h |1 +
tools/kvm/pci.c |1 -
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/include/kvm/pci.h b/tools/kvm/include
vesa, pci-shmem and virtio-pci devices need to set up config space with
little-endian conversions (as config space is LE). The pci_config_address
bitfield also needs to be reversed when building on BE systems.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/hw/pci-shmem.c | 23
The field size is currently wrong, read into a 32bit word instead of 16. This
casues trouble when BE.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/virtio/pci.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/virtio/pci.c b/tools/kvm/virtio/pci.c
The BAR addresses are set up fine, but missed the bar_size[] array which is now
updated correspondingly.
Use PCI_IO_SIZE instead of '0x100'.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/virtio/pci.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools
be read directly. This patch allows this sort of addressing.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/pci.h |5 +++
tools/kvm/pci.c | 63 +++---
2 files changed, 45 insertions(+), 23 deletions(-)
diff --git a/tools/kvm
pci_get_io_space_block() used to grab addresses from
KVM_32BIT_GAP_START + 0x100, which is x86-specific. Create a new define,
KVM_PCI_MMIO_AREA, to specify a bus address these allocations can come from.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/pci.c
(plus initrd).
(bzImages are not used on PPC, and this series does not add zImage support or an
ELF loader.) The intention is to later support loading firmware such as SLOF.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile | 10 +
tools/kvm/kvm.c
of a variety
of POWER CPUs should acquire this info from the host and encode appropriately.
This requires a 64-bit libfdt.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |3 +-
tools/kvm/powerpc/kvm.c | 141 +++
2 files changed
tree.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |2 +
tools/kvm/powerpc/kvm-cpu.c |5 +
tools/kvm/powerpc/kvm.c | 39 +-
tools/kvm/powerpc/spapr.h | 308 +++
tools/kvm/powerpc/spapr_hcall.c
, kvm__irq_line()
can be called to raise an IRQ on XICS.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |1 +
tools/kvm/powerpc/include/kvm/kvm-arch.h |1 +
tools/kvm/powerpc/include/kvm/kvm-cpu-arch.h |2 +
tools/kvm/powerpc/irq.c
This provides the PCI bridge, definitions for the address layout of the windows
and wires in IRQs. Once PCI devices are all registered, they are enumerated and
DT nodes generated for each.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/powerpc/include/kvm/kvm-arch.h |3 +
tools/kvm
PPC KVM doesn't yet support ioeventfds, so don't bomb out/die. virtio-pci is
able to function if it instead uses normal IO port notification.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/ioeventfd.h |3 ++-
tools/kvm/ioeventfd.c | 12 +---
tools
On 06/12/11 14:35, Matt Evans wrote:
This patch series rearranges and tidies various parts of kvmtool to pave the
way
for the addition of support for another architecture -- SPAPR PPC64. A second
patch series will follow to present the PPC64 support.
I forgot to mention, of course
Howdy Alex!
Alexander Graf wrote:
We will soon start and replace instructions from the text section with
other, paravirtualized versions. To ease the readability of those patches
I split out the generic looping and magic page mapping code out.
This patch still only contains stubs. But at
89 matches
Mail list logo
