On Tue, May 13, 2025 at 07:25:53PM +0800, Zixian Zeng wrote:
> On 25/04/30 01:32PM, Tom Rini wrote:
> > On Wed, Apr 30, 2025 at 02:26:04PM -0500, Bryan Brattlof wrote:
> > > On April 30, 2025 thus sayeth Tom Rini:
> > > > On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> > > >
On 25/04/30 01:32PM, Tom Rini wrote:
> On Wed, Apr 30, 2025 at 02:26:04PM -0500, Bryan Brattlof wrote:
> > On April 30, 2025 thus sayeth Tom Rini:
> > > On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> > > >
> > > >
> > > > On 4/30/2025 10:01 PM, Tom Rini wrote:
> > > > > On
On 25/04/30 01:32PM, Tom Rini wrote:
> On Wed, Apr 30, 2025 at 02:26:04PM -0500, Bryan Brattlof wrote:
> > On April 30, 2025 thus sayeth Tom Rini:
> > > On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> > > >
> > > >
> > > > On 4/30/2025 10:01 PM, Tom Rini wrote:
> > > > > On
On Wed, Apr 30, 2025 at 02:31:49PM -0500, Bryan Brattlof wrote:
> On April 30, 2025 thus sayeth Bryan Brattlof:
> > On April 30, 2025 thus sayeth Tom Rini:
> > > On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> > > >
> > > >
> > > > On 4/30/2025 10:01 PM, Tom Rini wrote:
>
On Wed, Apr 30, 2025 at 02:26:04PM -0500, Bryan Brattlof wrote:
> On April 30, 2025 thus sayeth Tom Rini:
> > On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> > >
> > >
> > > On 4/30/2025 10:01 PM, Tom Rini wrote:
> > > > On Wed, Apr 30, 2025 at 11:29:04AM -0500, Bryan Brat
On April 30, 2025 thus sayeth Bryan Brattlof:
> On April 30, 2025 thus sayeth Tom Rini:
> > On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> > >
> > >
> > > On 4/30/2025 10:01 PM, Tom Rini wrote:
> > > > On Wed, Apr 30, 2025 at 11:29:04AM -0500, Bryan Brattlof wrote:
> > >
On April 30, 2025 thus sayeth Tom Rini:
> On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
> >
> >
> > On 4/30/2025 10:01 PM, Tom Rini wrote:
> > > On Wed, Apr 30, 2025 at 11:29:04AM -0500, Bryan Brattlof wrote:
> > >> On April 30, 2025 thus sayeth Anshul Dalal:
> > >>> As di
On Wed, Apr 30, 2025 at 10:56:27PM +0530, Raghavendra, Vignesh wrote:
>
>
> On 4/30/2025 10:01 PM, Tom Rini wrote:
> > On Wed, Apr 30, 2025 at 11:29:04AM -0500, Bryan Brattlof wrote:
> >> On April 30, 2025 thus sayeth Anshul Dalal:
> >>> As discussed here[1], the go command causes undefined behav
On 4/30/2025 10:01 PM, Tom Rini wrote:
> On Wed, Apr 30, 2025 at 11:29:04AM -0500, Bryan Brattlof wrote:
>> On April 30, 2025 thus sayeth Anshul Dalal:
>>> As discussed here[1], the go command causes undefined behavior when used
>>> for running custom OSes since the icache might hold outdated da
On Wed, Apr 30, 2025 at 11:29:04AM -0500, Bryan Brattlof wrote:
> On April 30, 2025 thus sayeth Anshul Dalal:
> > As discussed here[1], the go command causes undefined behavior when used
> > for running custom OSes since the icache might hold outdated data. OSes
> > usually also expect the MMU to b
On April 30, 2025 thus sayeth Anshul Dalal:
> As discussed here[1], the go command causes undefined behavior when used
> for running custom OSes since the icache might hold outdated data. OSes
> usually also expect the MMU to be disabled upon execution.
>
> Therefore this patch adds a call to clea
On Wed, Apr 30, 2025 at 09:27:30PM +0530, Anshul Dalal wrote:
> On Wed Apr 30, 2025 at 7:46 PM IST, Tom Rini wrote:
> > On Wed, Apr 30, 2025 at 07:27:50PM +0530, Anshul Dalal wrote:
> >
> >> As discussed here[1], the go command causes undefined behavior when used
> >> for running custom OSes since
On Wed Apr 30, 2025 at 7:46 PM IST, Tom Rini wrote:
> On Wed, Apr 30, 2025 at 07:27:50PM +0530, Anshul Dalal wrote:
>
>> As discussed here[1], the go command causes undefined behavior when used
>> for running custom OSes since the icache might hold outdated data. OSes
>> usually also expect the MMU
On Wed, Apr 30, 2025 at 07:27:50PM +0530, Anshul Dalal wrote:
> As discussed here[1], the go command causes undefined behavior when used
> for running custom OSes since the icache might hold outdated data. OSes
> usually also expect the MMU to be disabled upon execution.
>
> Therefore this patch
As discussed here[1], the go command causes undefined behavior when used
for running custom OSes since the icache might hold outdated data. OSes
usually also expect the MMU to be disabled upon execution.
Therefore this patch adds a call to cleanup_before_linux before we jump
to the loaded program/
15 matches
Mail list logo