> Aleksandar: Can we use SEMIHOSTING on KVM MIPS?
>
You can assume the answer is no, we can't. But James Hogan, who maintains
MIPS KVM, may have different view, and his answer would override mine.
Yours,
Aleksandar
> For ARM Peter said:
>
> "semihosting hooks either SVC or HLT instructions, and
On 6/3/19 10:11 AM, Paolo Bonzini wrote:
> On 31/05/19 18:54, Miroslav Rezanina wrote:
>> What about CONFIG_ARM_VIRT - can we use it to introduce dependency on
>> CONFIG_SEMIHOSTING or is there valid scenario of qemu build with
>> CONFIG_ARM_VIRT
>> enabled and CONFIG_SEMIHOSTING disabled?
>
> If
On 31/05/19 18:54, Miroslav Rezanina wrote:
> What about CONFIG_ARM_VIRT - can we use it to introduce dependency on
> CONFIG_SEMIHOSTING or is there valid scenario of qemu build with
> CONFIG_ARM_VIRT
> enabled and CONFIG_SEMIHOSTING disabled?
If you are not really going to use TCG, disabling SEM
On Sat, 1 Jun 2019 at 10:34, Alex Bennée wrote:
>
>
> Peter Maydell writes:
> > Semihosting is a feature that works on all Arm CPUs
> > regardless of which machine model you're using (or whether
> > you're using softmmu or linux-user), so I think
> > the machine's Kconfig fragment is the wrong pl
Peter Maydell writes:
> On Fri, 31 May 2019 at 17:54, Miroslav Rezanina wrote:
>> What about CONFIG_ARM_VIRT - can we use it to introduce dependency on
>> CONFIG_SEMIHOSTING or is there valid scenario of qemu build with
>> CONFIG_ARM_VIRT
>> enabled and CONFIG_SEMIHOSTING disabled?
>
> Semiho
On Fri, 31 May 2019 at 17:40, Philippe Mathieu-Daudé wrote:
> I'll see what happened to Samuel series "Support disabling TCG on ARM"
> and see if it can be salvaged:
> https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg02451.html
That would certainly be useful.
> I suppose in this thread:
On Fri, 31 May 2019 at 17:54, Miroslav Rezanina wrote:
> What about CONFIG_ARM_VIRT - can we use it to introduce dependency on
> CONFIG_SEMIHOSTING or is there valid scenario of qemu build with
> CONFIG_ARM_VIRT
> enabled and CONFIG_SEMIHOSTING disabled?
Semihosting is a feature that works on al
Patchew URL: https://patchew.org/QEMU/20190531154735.20809-1-phi...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [RFC PATCH 0/2] target: Build with CONFIG_SEMIHOSTING
disabled
Type: series
Message-id
- Original Message -
> From: "Philippe Mathieu-Daudé"
> To: "Peter Maydell"
> Cc: "QEMU Developers" , "Paolo Bonzini"
> , "Miroslav Rezanina"
> , "Richard Henderson" ,
> "Aleksandar Rikalo"
> , "qemu-arm" , "Aleksandar
> Markovic" , "Aurelien
> Jarno" , "Alex Bennée" ,
> "Samuel Or
On 5/31/19 6:21 PM, Peter Maydell wrote:
> On Fri, 31 May 2019 at 16:47, Philippe Mathieu-Daudé
> wrote:
>>
>> Amusingly Miroslav and myself hit this issue at the same time.
>>
>> Currently there is no way to pass a CONFIG_X to sources in target/,
>> except via a Makefile rule (and filling with s
On Fri, 31 May 2019 at 16:47, Philippe Mathieu-Daudé wrote:
>
> Amusingly Miroslav and myself hit this issue at the same time.
>
> Currently there is no way to pass a CONFIG_X to sources in target/,
> except via a Makefile rule (and filling with stubs).
>
> Paolo says this is on purpose, CONFIG_X
Amusingly Miroslav and myself hit this issue at the same time.
Currently there is no way to pass a CONFIG_X to sources in target/,
except via a Makefile rule (and filling with stubs).
Paolo says this is on purpose, CONFIG_X selectors are meant for
devices and we try to avoid having config-devices
12 matches
Mail list logo
