Ping?
On 2019/4/15 10:39, Xiang Zheng wrote:
> On 2019/4/12 18:57, Kevin Wolf wrote:
>> Am 12.04.2019 um 11:50 hat Xiang Zheng geschrieben:
>>>
>>> On 2019/4/12 9:52, Xiang Zheng wrote:
On 2019/4/11 20:22, Kevin Wolf wrote:
> Okay, so your problem is that blk_pread() writes to the whole
On 2019/4/12 18:57, Kevin Wolf wrote:
> Am 12.04.2019 um 11:50 hat Xiang Zheng geschrieben:
>>
>> On 2019/4/12 9:52, Xiang Zheng wrote:
>>> On 2019/4/11 20:22, Kevin Wolf wrote:
Okay, so your problem is that blk_pread() writes to the whole buffer,
writing explicit zeroes for unallocated
Am 12.04.2019 um 11:50 hat Xiang Zheng geschrieben:
>
> On 2019/4/12 9:52, Xiang Zheng wrote:
> > On 2019/4/11 20:22, Kevin Wolf wrote:
> >> Okay, so your problem is that blk_pread() writes to the whole buffer,
> >> writing explicit zeroes for unallocated parts of the image, while you
> >> would
On 2019/4/12 9:52, Xiang Zheng wrote:
> On 2019/4/11 20:22, Kevin Wolf wrote:
>> Okay, so your problem is that blk_pread() writes to the whole buffer,
>> writing explicit zeroes for unallocated parts of the image, while you
>> would like to leave those parts of the buffer untouched so that we
On 2019/4/11 15:15, Markus Armbruster wrote:
>> For some historical reasons such as compatibility and extensibility[2], we
>> restrict both their size to 64MB -- both UEFI and qemu have cold hard
>> constants.
> These reasons aren't historical. But they're valid, and that's all that
> matters
On 2019/4/11 20:22, Kevin Wolf wrote:
> Okay, so your problem is that blk_pread() writes to the whole buffer,
> writing explicit zeroes for unallocated parts of the image, while you
> would like to leave those parts of the buffer untouched so that we don't
> actually allocate the memory, but can
Am 10.04.2019 um 10:36 hat Xiang Zheng geschrieben:
> Hi Kevin,
>
> On 2019/4/9 16:28, Kevin Wolf wrote:
> > Am 09.04.2019 um 08:01 hat Markus Armbruster geschrieben:
> >> László's last sentence below is "This really needs the attention of the
> >> block people." Cc'ing some.
> >>
> >> Laszlo
Xiang Zheng writes:
> Hi Kevin,
>
> On 2019/4/9 16:28, Kevin Wolf wrote:
>> Am 09.04.2019 um 08:01 hat Markus Armbruster geschrieben:
>>> László's last sentence below is "This really needs the attention of the
>>> block people." Cc'ing some.
>>>
>>> Laszlo Ersek writes:
>>>
On 04/08/19
Hi Kevin,
On 2019/4/9 16:28, Kevin Wolf wrote:
> Am 09.04.2019 um 08:01 hat Markus Armbruster geschrieben:
>> László's last sentence below is "This really needs the attention of the
>> block people." Cc'ing some.
>>
>> Laszlo Ersek writes:
>>
>>> On 04/08/19 15:43, Xiang Zheng wrote:
Am 09.04.2019 um 08:01 hat Markus Armbruster geschrieben:
> László's last sentence below is "This really needs the attention of the
> block people." Cc'ing some.
>
> Laszlo Ersek writes:
>
> > On 04/08/19 15:43, Xiang Zheng wrote:
> >>
> >> On 2019/4/3 23:35, Laszlo Ersek wrote:
> I
László's last sentence below is "This really needs the attention of the
block people." Cc'ing some.
Laszlo Ersek writes:
> On 04/08/19 15:43, Xiang Zheng wrote:
>>
>> On 2019/4/3 23:35, Laszlo Ersek wrote:
I thought about your comments and wrote the following patch (just for test)
On 2019/4/9 0:14, Laszlo Ersek wrote:
> On 04/08/19 15:43, Xiang Zheng wrote:
>>
>> On 2019/4/3 23:35, Laszlo Ersek wrote:
I thought about your comments and wrote the following patch (just for test)
which uses a file mapping to replace the anonymous mapping. UEFI seems to
work
On 04/08/19 15:43, Xiang Zheng wrote:
>
> On 2019/4/3 23:35, Laszlo Ersek wrote:
>>> I thought about your comments and wrote the following patch (just for test)
>>> which uses a file mapping to replace the anonymous mapping. UEFI seems to
>>> work
>>> fine. So why not use a file mapping to read
On 2019/4/3 23:35, Laszlo Ersek wrote:
>> I thought about your comments and wrote the following patch (just for test)
>> which uses a file mapping to replace the anonymous mapping. UEFI seems to
>> work
>> fine. So why not use a file mapping to read or write a pflash device?
> Honestly I can't
On 04/03/19 16:12, Xiang Zheng wrote:
> Hi Laszlo and Markus,
>
> Thanks for your useful suggestions and comments! :)
>
> On 2019/3/27 2:36, Markus Armbruster wrote:
>> Laszlo Ersek writes:
>>
>>> On 03/26/19 17:39, Markus Armbruster wrote:
Laszlo Ersek writes:
>>>
> With the dynamic
Hi Laszlo and Markus,
Thanks for your useful suggestions and comments! :)
On 2019/3/27 2:36, Markus Armbruster wrote:
> Laszlo Ersek writes:
>
>> On 03/26/19 17:39, Markus Armbruster wrote:
>>> Laszlo Ersek writes:
>>
With the dynamic sizing in QEMU (which, IIRC, I had originally
Laszlo Ersek writes:
> On 03/26/19 17:39, Markus Armbruster wrote:
>> Laszlo Ersek writes:
>
>>> With the dynamic sizing in QEMU (which, IIRC, I had originally
>>> introduced still in the 1MB times, due to the split between the
>>> executable and varstore parts), both the 1MB->2MB switch, and
On 03/26/19 17:39, Markus Armbruster wrote:
> Laszlo Ersek writes:
>> With the dynamic sizing in QEMU (which, IIRC, I had originally
>> introduced still in the 1MB times, due to the split between the
>> executable and varstore parts), both the 1MB->2MB switch, and the
>> 2MB->4MB switch in the
Laszlo Ersek writes:
> On 03/26/19 07:17, Markus Armbruster wrote:
>> Zheng Xiang writes:
>>
>>> Hi Peter,
>>>
>>> Thanks for your reply!
>>>
>>> On 2019/3/25 21:11, Peter Maydell wrote:
On Mon, 25 Mar 2019 at 12:53, Xiang Zheng wrote:
>
> Currently we fill the VIRT_FLASH space
On 03/26/19 07:17, Markus Armbruster wrote:
> Zheng Xiang writes:
>
>> Hi Peter,
>>
>> Thanks for your reply!
>>
>> On 2019/3/25 21:11, Peter Maydell wrote:
>>> On Mon, 25 Mar 2019 at 12:53, Xiang Zheng wrote:
Currently we fill the VIRT_FLASH space with two 64MB NOR images when
Zheng Xiang writes:
> Hi Peter,
>
> Thanks for your reply!
>
> On 2019/3/25 21:11, Peter Maydell wrote:
>> On Mon, 25 Mar 2019 at 12:53, Xiang Zheng wrote:
>>>
>>> Currently we fill the VIRT_FLASH space with two 64MB NOR images when
>>> using persistent UEFI variables on QEMU. Actually we only
Hi Peter,
Thanks for your reply!
On 2019/3/25 21:11, Peter Maydell wrote:
> On Mon, 25 Mar 2019 at 12:53, Xiang Zheng wrote:
>>
>> Currently we fill the VIRT_FLASH space with two 64MB NOR images when
>> using persistent UEFI variables on QEMU. Actually we only use a very
>> small part of the
On 03/25/19 14:11, Peter Maydell wrote:
> On Mon, 25 Mar 2019 at 12:53, Xiang Zheng wrote:
>>
>> Currently we fill the VIRT_FLASH space with two 64MB NOR images when
>> using persistent UEFI variables on QEMU. Actually we only use a very
>> small part of the memory while the rest significant
On Mon, 25 Mar 2019 at 12:53, Xiang Zheng wrote:
>
> Currently we fill the VIRT_FLASH space with two 64MB NOR images when
> using persistent UEFI variables on QEMU. Actually we only use a very
> small part of the memory while the rest significant large part of
> memory is wasted.
>
> This patch
Currently we fill the VIRT_FLASH space with two 64MB NOR images when
using persistent UEFI variables on QEMU. Actually we only use a very
small part of the memory while the rest significant large part of
memory is wasted.
This patch creates and maps a variable size of flash device instead of
a
25 matches
Mail list logo
