Jordan Justen writes:
> On Fri, Mar 22, 2013 at 12:48 PM, Markus Armbruster wrote:
>> Jordan Justen writes:
>>
>>> On Thu, Mar 21, 2013 at 12:45 AM, Markus Armbruster
>>> wrote:
x86 maintainers may wish to *switch it off* until it's done fully and
properly, by setting "pc-sysfw" prop
On 04/08/2013 04:43 PM, Gleb Natapov wrote:
> On Mon, Apr 08, 2013 at 01:18:10AM -0700, Jordan Justen wrote:
>> On Sun, Apr 7, 2013 at 11:06 PM, Xiao Guangrong
>> wrote:
>>> On 03/23/2013 03:09 AM, Jordan Justen wrote:
>>>
Admittedly, I've been completely ineffectual in resolving the kvm
On Mon, Apr 08, 2013 at 01:18:10AM -0700, Jordan Justen wrote:
> On Sun, Apr 7, 2013 at 11:06 PM, Xiao Guangrong
> wrote:
> > On 03/23/2013 03:09 AM, Jordan Justen wrote:
> >
> >> Admittedly, I've been completely ineffectual in resolving the kvm
> >> portion. More recently I tried to make use of K
On Sun, Apr 7, 2013 at 11:06 PM, Xiao Guangrong
wrote:
> On 03/23/2013 03:09 AM, Jordan Justen wrote:
>
>> Admittedly, I've been completely ineffectual in resolving the kvm
>> portion. More recently I tried to make use of KVM_MEM_READONLY to
>> address this. I was able to get an VM exit on writes
On 03/23/2013 03:09 AM, Jordan Justen wrote:
> Admittedly, I've been completely ineffectual in resolving the kvm
> portion. More recently I tried to make use of KVM_MEM_READONLY to
> address this. I was able to get an VM exit on writes to flash, but not
> able to get the memory region to convert t
On Fri, Mar 22, 2013 at 12:48 PM, Markus Armbruster wrote:
> Jordan Justen writes:
>
>> On Thu, Mar 21, 2013 at 12:45 AM, Markus Armbruster
>> wrote:
>>> x86 maintainers may wish to *switch it off* until it's done fully and
>>> properly, by setting "pc-sysfw" property "rom_only" to 1.
>>
>> Thi
On 03/22/13 20:48, Markus Armbruster wrote:
> Jordan Justen writes:
>>> 1. The "pc-sysfw" device is mostly harmless.
>>
>> Indeed, and it's only marginally of interest until kvm supports it.
>>
>> Admittedly, I've been completely ineffectual in resolving the kvm
>> portion. More recently I tried
Jordan Justen writes:
> On Thu, Mar 21, 2013 at 12:45 AM, Markus Armbruster wrote:
>> x86 maintainers may wish to *switch it off* until it's done fully and
>> properly, by setting "pc-sysfw" property "rom_only" to 1.
>
> This would completely disable the flash support.
Unless the user enables i
On Thu, Mar 21, 2013 at 12:45 AM, Markus Armbruster wrote:
> x86 maintainers may wish to *switch it off* until it's done fully and
> properly, by setting "pc-sysfw" property "rom_only" to 1.
This would completely disable the flash support. At the time this
feature was added, I think it was well u
Peter Maydell writes:
> On 21 March 2013 07:45, Markus Armbruster wrote:
>> [Note cc: Jordan, who added flash to x86 in commit bd183c79]
>>
>> Peter Maydell writes:
>>
>>> These patches implement migration support for pflash_cfi01.
>>> The first patch just drops some useless state so we don't
>
On 21 March 2013 07:45, Markus Armbruster wrote:
> [Note cc: Jordan, who added flash to x86 in commit bd183c79]
>
> Peter Maydell writes:
>
>> These patches implement migration support for pflash_cfi01.
>> The first patch just drops some useless state so we don't
>> have to think about it for mig
[Note cc: Jordan, who added flash to x86 in commit bd183c79]
Peter Maydell writes:
> These patches implement migration support for pflash_cfi01.
> The first patch just drops some useless state so we don't
> have to think about it for migration.
>
> NB that pflash_cfi01 is used in the x86 pc mode
12 matches
Mail list logo
