linux-kernel - Re: [PATCH v2 01/15] x86/e820: remove conditional early mapping in parse_e820

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110114134345.712e2e29@queued.net>
Date:	Fri, 14 Jan 2011 13:43:45 -0800
From:	Andres Salomon <dilinger@...ued.net>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	linux-kernel@...r.kernel.org, sodaville@...utronix.de,
	x86@...nel.org, dirk.brandewie@...il.com, dsd@...top.org
Subject: Re: [PATCH v2 01/15] x86/e820: remove conditional early mapping in
 parse_e820_ext

On Fri, 14 Jan 2011 11:57:09 +0100
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:

> * Grant Likely | 2011-01-14 01:14:46 [-0700]:
> 
> >Hey Sebastian,
> Hi Grant,
> 
> thanks for doing this.
> 
> >Can you please repost this series after the merge window closes?
> >Some of the patches have been reworked and reposted, but I've kind
> >of lost track of which ones need my attention.  Also, some of the
> >patches have
> Yes, this was my secret plan :) I also had to rework patches because
> of other patches either because they no longer applied or because the
> code had to change in order to work again.
> 
> In case "[v2,13/15] x86/rtc: don't register rtc if we the DT blob" [0]
> goes into the category "lost track" and not "had no time to reply"
> could please take a look? The important part is where it could change
> behavior for OLPC and it migh end up without a RTC. I Cc Andres
> Salomon as might know where the RTC on OLPC is comming from.

The RTC that OLPC uses for XO-1 was interspersed w/ the power management
stuff, so it hasn't gone upstream yet (dsd is still working on the pm
stuff). Thus, for Linus kernels the XO-1 uses rtc_cmos; so yes, this
could break things.

On OLPC kernels on the XO-1, we read RTC information from the
CS5536's MSRs (note that there's nothing there that's OLPC-specific, so
this should probably become a generic geode RTC driver).  I'm unfamiliar
with the XO-1.5, but it appears we use the VX855 RTC (at least for
wakeups). I don't see a specific RTC driver for it, so I suspect it
relies on rtc_cmos.


> 
> >gone in via the tip tree, so it would be useful to regroup and figure
> >out which ones are no longer needed.
> I try to regroup and a add TIP or OF prefix.
> 
> >I'll be able to take a fresh look and pick up the ones that are ready
> >after the merge window closes.
> Okay.
> 
> >Thanks,
> >g.
> 
> [0] https://patchwork.kernel.org/patch/450681/
> 
> Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/