> On Fri, Feb 2, 2018 at 1:49 PM, Alistair Francis
> wrote:
>> On Fri, Feb 2, 2018 at 12:37 PM, Alex Bennée wrote:
>>>
>>> Alistair Francis writes:
>>>
On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
wrote:
> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée
> wrote:
>>
>
On Fri, Feb 2, 2018 at 1:49 PM, Alistair Francis
wrote:
> On Fri, Feb 2, 2018 at 12:37 PM, Alex Bennée wrote:
>>
>> Alistair Francis writes:
>>
>>> On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
>>> wrote:
On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée wrote:
>
> Alistair Francis
On Fri, Feb 2, 2018 at 12:37 PM, Alex Bennée wrote:
>
> Alistair Francis writes:
>
>> On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
>> wrote:
>>> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée wrote:
Alistair Francis writes:
> On Wed, Jan 31, 2018 at 12:32 PM, Alex Bennée
Alistair Francis writes:
> On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
> wrote:
>> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée wrote:
>>>
>>> Alistair Francis writes:
>>>
On Wed, Jan 31, 2018 at 12:32 PM, Alex Bennée
wrote:
>
> Alistair Francis writes:
>
>> O
On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
wrote:
> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée wrote:
>>
>> Alistair Francis writes:
>>
>>> On Wed, Jan 31, 2018 at 12:32 PM, Alex Bennée
>>> wrote:
Alistair Francis writes:
> On Tue, Jan 30, 2018 at 8:26 PM, Paolo Bonz
On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée wrote:
>
> Alistair Francis writes:
>
>> On Wed, Jan 31, 2018 at 12:32 PM, Alex Bennée wrote:
>>>
>>> Alistair Francis writes:
>>>
On Tue, Jan 30, 2018 at 8:26 PM, Paolo Bonzini wrote:
> On 30/01/2018 18:56, Alistair Francis wrote:
>>
>>
Alistair Francis writes:
> On Wed, Jan 31, 2018 at 12:32 PM, Alex Bennée wrote:
>>
>> Alistair Francis writes:
>>
>>> On Tue, Jan 30, 2018 at 8:26 PM, Paolo Bonzini wrote:
On 30/01/2018 18:56, Alistair Francis wrote:
>
> I don't have a good solution though, as setting CPU_INTERRU
On Wed, Jan 31, 2018 at 12:32 PM, Alex Bennée wrote:
>
> Alistair Francis writes:
>
>> On Tue, Jan 30, 2018 at 8:26 PM, Paolo Bonzini wrote:
>>> On 30/01/2018 18:56, Alistair Francis wrote:
I don't have a good solution though, as setting CPU_INTERRUPT_RESET
doesn't help (that isn'
Alistair Francis writes:
> On Tue, Jan 30, 2018 at 8:26 PM, Paolo Bonzini wrote:
>> On 30/01/2018 18:56, Alistair Francis wrote:
>>>
>>> I don't have a good solution though, as setting CPU_INTERRUPT_RESET
>>> doesn't help (that isn't handled while we are halted) and
>>> async_run_on_cpu()/run_o
On Wed, Jan 31, 2018 at 10:59 AM, Peter Maydell
wrote:
> On 31 January 2018 at 18:51, Alistair Francis wrote:
>> On Wed, Jan 31, 2018 at 10:48 AM, Peter Maydell
>> wrote:
>>> On 31 January 2018 at 18:17, Alistair Francis wrote:
On Wed, Jan 31, 2018 at 9:13 AM, Paolo Bonzini wrote:
> c
On 31 January 2018 at 18:51, Alistair Francis wrote:
> On Wed, Jan 31, 2018 at 10:48 AM, Peter Maydell
> wrote:
>> On 31 January 2018 at 18:17, Alistair Francis wrote:
>>> On Wed, Jan 31, 2018 at 9:13 AM, Paolo Bonzini wrote:
cpu->halted = false likewise should not be needed here, but you
On Wed, Jan 31, 2018 at 10:51 AM, Alistair Francis wrote:
> On Wed, Jan 31, 2018 at 10:48 AM, Peter Maydell
> wrote:
>> On 31 January 2018 at 18:17, Alistair Francis wrote:
>>> On Wed, Jan 31, 2018 at 9:13 AM, Paolo Bonzini wrote:
cpu->halted = false likewise should not be needed here, but
On Wed, Jan 31, 2018 at 10:48 AM, Peter Maydell
wrote:
> On 31 January 2018 at 18:17, Alistair Francis wrote:
>> On Wed, Jan 31, 2018 at 9:13 AM, Paolo Bonzini wrote:
>>> cpu->halted = false likewise should not be needed here, but you cannot
>>> just clear CPU_INTERRUPT_HALT either. You need to
On 31 January 2018 at 18:17, Alistair Francis wrote:
> On Wed, Jan 31, 2018 at 9:13 AM, Paolo Bonzini wrote:
>> cpu->halted = false likewise should not be needed here, but you cannot
>> just clear CPU_INTERRUPT_HALT either. You need to set a *different*
>> interrupt request bit (the dummy CPU_IN
On Wed, Jan 31, 2018 at 9:13 AM, Paolo Bonzini wrote:
> On 03/01/2018 17:10, Alistair Francis wrote:
>> Hey guys, I'm super stuck with an ugly MTTCG issue and was wondering
>> if anyone had any ideas.
>>
>> In the Xilinx fork of QEMU (based on 2.11) we have a way for CPUs to
>> halt other CPUs. Th
On 03/01/2018 17:10, Alistair Francis wrote:
> Hey guys, I'm super stuck with an ugly MTTCG issue and was wondering
> if anyone had any ideas.
>
> In the Xilinx fork of QEMU (based on 2.11) we have a way for CPUs to
> halt other CPUs. This is used for example when the power control unit
> halts th
On Tue, Jan 30, 2018 at 8:26 PM, Paolo Bonzini wrote:
> On 30/01/2018 18:56, Alistair Francis wrote:
>>
>> I don't have a good solution though, as setting CPU_INTERRUPT_RESET
>> doesn't help (that isn't handled while we are halted) and
>> async_run_on_cpu()/run_on_cpu() doesn't reliably reset the
On 30/01/2018 18:56, Alistair Francis wrote:
>
> I don't have a good solution though, as setting CPU_INTERRUPT_RESET
> doesn't help (that isn't handled while we are halted) and
> async_run_on_cpu()/run_on_cpu() doesn't reliably reset the CPU when we
> want.
>
> I've ever tried pausing all CPUs be
On Fri, Jan 5, 2018 at 6:23 PM, Alistair Francis wrote:
> On Thu, Jan 4, 2018 at 3:08 AM, Alex Bennée wrote:
>>
>> Alistair Francis writes:
>>
>>> Hey guys, I'm super stuck with an ugly MTTCG issue and was wondering
>>> if anyone had any ideas.
>>>
>>> In the Xilinx fork of QEMU (based on 2.11)
On Thu, Jan 4, 2018 at 3:08 AM, Alex Bennée wrote:
>
> Alistair Francis writes:
>
>> Hey guys, I'm super stuck with an ugly MTTCG issue and was wondering
>> if anyone had any ideas.
>>
>> In the Xilinx fork of QEMU (based on 2.11) we have a way for CPUs to
>> halt other CPUs. This is used for exa
Alistair Francis writes:
> Hey guys, I'm super stuck with an ugly MTTCG issue and was wondering
> if anyone had any ideas.
>
> In the Xilinx fork of QEMU (based on 2.11) we have a way for CPUs to
> halt other CPUs. This is used for example when the power control unit
> halts the ARM A53s. To do
On Wed, Jan 3, 2018 at 2:23 PM, Alistair Francis wrote:
> On Wed, Jan 3, 2018 at 2:14 PM, Peter Maydell
> wrote:
>> On 3 January 2018 at 22:10, Alistair Francis wrote:
>>> Any chance any one has some insight into a way to externally set a
>>> vCPU as halted/un-halted?
>>
>> PSCI (where one vCPU
On Wed, Jan 3, 2018 at 2:14 PM, Peter Maydell wrote:
> On 3 January 2018 at 22:10, Alistair Francis wrote:
>> Any chance any one has some insight into a way to externally set a
>> vCPU as halted/un-halted?
>
> PSCI (where one vCPU can power off another) does this by
> calling arm_set_cpu_off(). D
On 3 January 2018 at 22:10, Alistair Francis wrote:
> Any chance any one has some insight into a way to externally set a
> vCPU as halted/un-halted?
PSCI (where one vCPU can power off another) does this by
calling arm_set_cpu_off(). Does that (or some variation
on it) work?
thanks
-- PMM
Hey guys, I'm super stuck with an ugly MTTCG issue and was wondering
if anyone had any ideas.
In the Xilinx fork of QEMU (based on 2.11) we have a way for CPUs to
halt other CPUs. This is used for example when the power control unit
halts the ARM A53s. To do this we have internal GPIO signals that
25 matches
Mail list logo
