On 8/9/22 11:17, Michael S. Tsirkin wrote:
1) if we believe "build setup_data in QEMU" is a feasible design that only
needs more yak shaving, we can keep the code in, but disabled by default,
and sort it out in 7.2.
2) if we go for an alternative design, it needs to be reverted. For example
On Tue, Aug 09, 2022 at 10:07:44AM -0400, Michael S. Tsirkin wrote:
> On Tue, Aug 09, 2022 at 02:17:23PM +0200, Jason A. Donenfeld wrote:
> > Hey Paolo,
> >
> > On Fri, Aug 05, 2022 at 02:47:27PM +0200, Jason A. Donenfeld wrote:
> > > Hi Paolo,
> > >
> > > On Fri, Aug 05, 2022 at 10:10:02AM
On Tue, Aug 09, 2022 at 02:17:23PM +0200, Jason A. Donenfeld wrote:
> Hey Paolo,
>
> On Fri, Aug 05, 2022 at 02:47:27PM +0200, Jason A. Donenfeld wrote:
> > Hi Paolo,
> >
> > On Fri, Aug 05, 2022 at 10:10:02AM +0200, Paolo Bonzini wrote:
> > > On 8/5/22 01:04, Jason A. Donenfeld wrote:
> > > > +
Hey Paolo,
On Fri, Aug 05, 2022 at 02:47:27PM +0200, Jason A. Donenfeld wrote:
> Hi Paolo,
>
> On Fri, Aug 05, 2022 at 10:10:02AM +0200, Paolo Bonzini wrote:
> > On 8/5/22 01:04, Jason A. Donenfeld wrote:
> > > +/* Nothing else uses this part of the hardware mapped region */
> > > +
On Fri, Aug 05, 2022 at 07:29:29PM +0200, Paolo Bonzini wrote:
> On 8/5/22 13:08, Ard Biesheuvel wrote:
> > >
> > > Does it work to place setup_data at the end of the cmdline file instead
> > > of having it at the end of the kernel file? This way the first item
> > > will be at 0x2 +
On Fri, 5 Aug 2022 at 19:29, Paolo Bonzini wrote:
>
> On 8/5/22 13:08, Ard Biesheuvel wrote:
> >>
> >> Does it work to place setup_data at the end of the cmdline file instead
> >> of having it at the end of the kernel file? This way the first item
> >> will be at 0x2 + cmdline_size.
> >>
> >
On 8/5/22 13:08, Ard Biesheuvel wrote:
Does it work to place setup_data at the end of the cmdline file instead
of having it at the end of the kernel file? This way the first item
will be at 0x2 + cmdline_size.
Does QEMU always allocate the command line statically like that?
AFAIK, OVMF
On 08/05/22 14:47, Jason A. Donenfeld wrote:
> Hi Paolo,
>
> On Fri, Aug 05, 2022 at 10:10:02AM +0200, Paolo Bonzini wrote:
>> On 8/5/22 01:04, Jason A. Donenfeld wrote:
>>> +/* Nothing else uses this part of the hardware mapped region */
>>> +setup_data_base = 0xf - 0x1000;
>>
>>
Hi Paolo,
On Fri, Aug 05, 2022 at 10:10:02AM +0200, Paolo Bonzini wrote:
> On 8/5/22 01:04, Jason A. Donenfeld wrote:
> > +/* Nothing else uses this part of the hardware mapped region */
> > +setup_data_base = 0xf - 0x1000;
>
> Isn't this where the BIOS lives? I don't think this
On Fri, 5 Aug 2022 at 10:10, Paolo Bonzini wrote:
>
> On 8/5/22 01:04, Jason A. Donenfeld wrote:
> > +/* Nothing else uses this part of the hardware mapped region */
> > +setup_data_base = 0xf - 0x1000;
>
> Isn't this where the BIOS lives? I don't think this works.
>
> Does it work
On 8/5/22 01:04, Jason A. Donenfeld wrote:
+/* Nothing else uses this part of the hardware mapped region */
+setup_data_base = 0xf - 0x1000;
Isn't this where the BIOS lives? I don't think this works.
Does it work to place setup_data at the end of the cmdline file instead
of
11 matches
Mail list logo
