On 04/01/14 03:22, Peter Maydell wrote:
On 1 April 2014 01:35, Michael Casadevall wrote:
Its a fairly major improvement, and I managed to use GdbSyms.dll to
load ALL the symbol files in a single go, but I'm still having issues
with the stack. At least now i can get the frame we're currently in
On 1 April 2014 01:35, Michael Casadevall wrote:
> Its a fairly major improvement, and I managed to use GdbSyms.dll to
> load ALL the symbol files in a single go, but I'm still having issues
> with the stack. At least now i can get the frame we're currently in
> reliably, but the backtrace remains
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2014 06:27 PM, Peter Maydell wrote:
> On 31 March 2014 23:07, Michael Casadevall
> wrote:
>> On 03/28/2014 07:40 PM, Peter Maydell wrote:
>>> There's a bug in QEMU's AArch64 KVM support which means we
>>> don't do the right thing with SP o
On 31 March 2014 23:07, Michael Casadevall
wrote:
> On 03/28/2014 07:40 PM, Peter Maydell wrote:
>> There's a bug in QEMU's AArch64 KVM support which means we don't
>> do the right thing with SP on syncing state to/from the kernel, so
>> don't trust that (Fixed either in master or in my a64-sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2014 07:40 PM, Peter Maydell wrote:
>> .
> There's a bug in QEMU's AArch64 KVM support which means we don't
> do the right thing with SP on syncing state to/from the kernel, so
> don't trust that (Fixed either in master or in my a64-sys
On 28 March 2014 20:08, Michael Casadevall
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/28/2014 03:47 PM, Christoffer Dall wrote:
>> On Fri, Mar 28, 2014 at 03:38:28PM -0400, Michael Casadevall
>> wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>>
>>>
>>>
>>> On
On Fri, Mar 28, 2014 at 08:57:15PM -0400, Michael Casadevall wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/28/2014 08:17 PM, Christoffer Dall wrote:
> > On Fri, Mar 28, 2014 at 07:17:49PM -0400, Michael Casadevall
> > wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2014 08:17 PM, Christoffer Dall wrote:
> On Fri, Mar 28, 2014 at 07:17:49PM -0400, Michael Casadevall
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>>
>>
>> On 03/28/2014 05:29 PM, Christoffer Dall wrote:
>>> On Fri, Mar 28
On Fri, Mar 28, 2014 at 07:17:49PM -0400, Michael Casadevall wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/28/2014 05:29 PM, Christoffer Dall wrote:
> > On Fri, Mar 28, 2014 at 05:08:03PM -0400, Michael Casadevall
> > wrote:
>
> > if you run the interrupt handler you ar
On 28 March 2014 19:38, Michael Casadevall
wrote:
> On 03/28/2014 02:09 PM, Christoffer Dall wrote:
>> On Fri, Mar 28, 2014 at 04:26:59AM -0400, Michael Casadevall
>> wrote:
>>> Previous attempts to debug assets shows that EFI does "odd"
>>> things to the stack when we hit an exception, making wal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2014 05:29 PM, Christoffer Dall wrote:
> On Fri, Mar 28, 2014 at 05:08:03PM -0400, Michael Casadevall
> wrote:
> if you run the interrupt handler you are not stuck in wfi, but
> re-execute it, and it's your software wait condition which is
On Fri, Mar 28, 2014 at 05:08:03PM -0400, Michael Casadevall wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/28/2014 05:02 PM, Christoffer Dall wrote:
> > On Fri, Mar 28, 2014 at 04:08:52PM -0400, Michael Casadevall
> > wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2014 05:02 PM, Christoffer Dall wrote:
> On Fri, Mar 28, 2014 at 04:08:52PM -0400, Michael Casadevall
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>>
>>
>> On 03/28/2014 03:47 PM, Christoffer Dall wrote:
>>> On Fri, Mar 28
On Fri, Mar 28, 2014 at 04:08:52PM -0400, Michael Casadevall wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/28/2014 03:47 PM, Christoffer Dall wrote:
> > On Fri, Mar 28, 2014 at 03:38:28PM -0400, Michael Casadevall
> > wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2014 03:47 PM, Christoffer Dall wrote:
> On Fri, Mar 28, 2014 at 03:38:28PM -0400, Michael Casadevall
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>>
>>
>> On 03/28/2014 02:09 PM, Christoffer Dall wrote:
>>> On Fri, Mar 28
On Fri, Mar 28, 2014 at 03:38:28PM -0400, Michael Casadevall wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 03/28/2014 02:09 PM, Christoffer Dall wrote:
> > On Fri, Mar 28, 2014 at 04:26:59AM -0400, Michael Casadevall
> > wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2014 02:09 PM, Christoffer Dall wrote:
> On Fri, Mar 28, 2014 at 04:26:59AM -0400, Michael Casadevall
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> As I've made a fair bit of headway since LinaroConnect, I wanted
>> to dro
On Fri, Mar 28, 2014 at 04:26:59AM -0400, Michael Casadevall wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> As I've made a fair bit of headway since LinaroConnect, I wanted to
> drop a line on my current progress with porting TianoCore to KVM
>
> Summary (tl;dr version):
>
> KVM ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As I've made a fair bit of headway since LinaroConnect, I wanted to
drop a line on my current progress with porting TianoCore to KVM
Summary (tl;dr version):
KVM can start TianoCore, and boot all the way to shell, and access
HDDs via VirtioBlk. We ca
19 matches
Mail list logo