On Fri, Apr 24, 2015 at 01:28:44PM -0700, Peter Crosthwaite wrote:
> Connect the GPIO outputs from the individual CPUs for the timers to the
> GIC.
>
> Tested-by: Alistair Francis
> Signed-off-by: Peter Crosthwaite
Reviewed-by: Edgar E. Iglesias
> ---
> changed since v4:
> Use macro for GIC_
On Mon, May 4, 2015 at 8:26 PM, Edgar E. Iglesias
wrote:
> On Fri, Apr 24, 2015 at 01:28:48PM -0700, Peter Crosthwaite wrote:
>> Add a machine model for the Xilinx ZynqMP SoC EP108 board.
>
> hmm, I think xlnx-ep108 is quite cryptic as user input. Can't we just
> name this xilinx-ep108?
>
So I wa
On Mon, May 04, 2015 at 09:00:46PM -0700, Peter Crosthwaite wrote:
> On Mon, May 4, 2015 at 8:26 PM, Edgar E. Iglesias
> wrote:
> > On Fri, Apr 24, 2015 at 01:28:48PM -0700, Peter Crosthwaite wrote:
> >> Add a machine model for the Xilinx ZynqMP SoC EP108 board.
> >
> > hmm, I think xlnx-ep108 is
Migrate the target_disas TARGET_MICROBLAZE code to common code, so
that the disassambly works for the monitor (as well the log).
E.g.
(qemu) xp 0x9000
9000: 0x94208001
And before this patch:
(qemu) xp/i 0x9000
0x9000: Asm output not supported on this arch
After:
(qemu) xp
Migrate the target_disas TARGET_CRIS code to common code, so that
the disassambly works for the monitor (as well the log).
E.g.
(qemu) xp 0x40004000
40004000: 0x1e6f25f0
And before this patch:
(qemu) xp/i 0x40004000
0x40004000: Asm output not supported on this arch
After:
(qemu) xp/i 0x4
There two functions are mostly trying to do the same thing, which is
disassemble a target instruction (sequence) for printfing. The
architecture specific setup is largely duped between the two functions.
Most architectures are carbon copy and can be factored out without
issue (P1). Three architectu
The monitor_ and target_ disas function do mostly the same thing.
One dissambles target instructions on behalf of the log, the other
for the monitor command "xp/i" and friends.
There is a #if defined TARGET_FOO switch duplicated between both
functions and arch-specific setup for disas is copied be
Cris has the complication of variable length instructions and has
a check in place to clamp memory reads in case the disas request
doesn't have enough bytes for the instruction being disas'd. This
breaks down in the case where disassembling for the monitor where
the buffer length is defaulted to 0.
In a normal disassembly flow, the printf and stream being used varies
from disas job to job. In particular it varies if mixing monitor_disas
and target_disas.
Make both the printfer function and target stream settable in the
QEMUDisassmbler class. Remove the stream_ initialisation from the
constru
Add the ARM specific disassembly flags setup, so ARM can be correctly
disassembled from the monitor.
Signed-off-by: Peter Crosthwaite
---
monitor.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/monitor.c b/monitor.c
index d831d98..9d9f1e2 100644
--- a/monitor.c
+++ b/monitor.c
As it is more fully featured. It has multi-endian, thumb and AArch64
support whereas the existing monitor disas support only has vanilla
AA32 support.
E.G. Running an AA64 linux kernel the follow -d in_asm disas happens
(taget_disas()):
IN:
0x4000: 58c0 ldr x0, pc+24 (addr 0
On Fri, Apr 24, 2015 at 01:28:45PM -0700, Peter Crosthwaite wrote:
> Create a new header for Cadence GEM to allow using the device with
> modern SoC programming conventions. The state struct needs to be
> visible to embed the device in SoC containers.
>
> Reviewed-by: Alistair Francis
> Reviewed-
On Tue, 5 May 2015 11:00:01 +1000
David Gibson wrote:
> qemu currently implements the hypercalls H_LOGICAL_CI_LOAD and
> H_LOGICAL_CI_STORE as PAPR extensions. These are used by the SLOF firmware
> for IO, because performing cache inhibited MMIO accesses with the MMU off
> (real mode) is very a
201 - 213 of 213 matches
Mail list logo
