From: Dave Hansen <dave.han...@linux.intel.com>
I'm seeing warnings on kernel configurations where CONFIG_PM is
disabled. It happens in 4.12, at least:
drivers/ethernet/intel/igb/igb_main.c:7988:13: warning:
'igb_deliver_wake_packet' defined but not used [-Wunused-function]
This is b
On 10/19/2016 10:01 AM, Michal Hocko wrote:
> The question I had earlier was whether this has to be an explicit FOLL
> flag used by g-u-p users or we can just use it internally when mm !=
> current->mm
The reason I chose not to do that was that deferred work gets run under
a basically random
On 10/19/2016 02:07 AM, Michal Hocko wrote:
> On Wed 19-10-16 09:58:15, Lorenzo Stoakes wrote:
>> On Tue, Oct 18, 2016 at 05:30:50PM +0200, Michal Hocko wrote:
>>> I am wondering whether we can go further. E.g. it is not really clear to
>>> me whether we need an explicit FOLL_REMOTE when we can in
On 08/31/2015 02:26 PM, Dave Hansen wrote:
> From: Dave Hansen <dave.han...@linux.intel.com>
>
> I have a .config with CONFIG_PM disabled. I get the following whenever
> compiling the e1000 driver:
>
> ...net/ethernet/intel/e1000e/netdev.c:6450:13: warning:
>
From: Dave Hansen <dave.han...@linux.intel.com>
I have a .config with CONFIG_PM disabled. I get the following whenever
compiling the e1000 driver:
...net/ethernet/intel/e1000e/netdev.c:6450:13: warning:
'e1000e_disable_aspm_locked' defined but not used [-Wunused-function]
stati
On Mon, 2008-02-18 at 11:00 +0100, Jan-Bernd Themann wrote:
Dave Hansen [EMAIL PROTECTED] wrote on 15.02.2008 17:55:38:
I've been thinking about that, and I don't think you really *need* to
keep a comprehensive map like that.
When the memory is in a particular configuration (range
On Fri, 2008-02-15 at 14:22 +0100, Christoph Raisch wrote:
A translation from kernel to ehea_bmap space should be fast and
predictable
(ruling out hashes).
If a driver doesn't know anything else about the mapping structure,
the normal solution in kernel for this type of problem is a multi
On Thu, 2008-02-14 at 09:46 +0100, Christoph Raisch wrote:
Dave Hansen [EMAIL PROTECTED] wrote on 13.02.2008 18:05:00:
On Wed, 2008-02-13 at 16:17 +0100, Jan-Bernd Themann wrote:
Constraints imposed by HW / FW:
- eHEA has own MMU
- eHEA Memory Regions (MRs) are used by the eHEA MMU
On Thu, 2008-02-14 at 09:36 -0800, Badari Pulavarty wrote:
I am not sure what you are trying to do with walk_memory_resource().
The
behavior is different on ppc64. Hotplug memory usage assumes that all
the memory resources (all system memory, not just IOMEM) are
represented
in
On Wed, 2008-02-13 at 16:17 +0100, Jan-Bernd Themann wrote:
Constraints imposed by HW / FW:
- eHEA has own MMU
- eHEA Memory Regions (MRs) are used by the eHEA MMU to translate virtual
addresses to absolute addresses (like DMA mapped memory on a PCI bus)
- The number of MRs is limited
On Mon, 2008-02-11 at 17:24 +0100, Jan-Bernd Themann wrote:
Drivers like eHEA need memory notifiers in order to
update their internal DMA memory map when memory is added
to or removed from the system.
Patch for eHEA memory hotplug support that uses these functions:
On Mon, 2008-02-11 at 17:24 +0100, Jan-Bernd Themann wrote:
Drivers like eHEA need memory notifiers in order to
update their internal DMA memory map when memory is added
to or removed from the system.
Patch for eHEA memory hotplug support that uses these functions:
On Mon, 2008-02-11 at 16:57 +0100, Jan-Bernd Themann wrote:
Drivers like eHEA need memory notifiers in order to
update their internal DMA memory map when memory is added
to or removed from the system.
Could you post this with the new users as well so we can make sure
they're not abusing this
On Mon, 2008-02-11 at 17:24 +0100, Jan-Bernd Themann wrote:
the eHEA patch belongs to a patchset that is usually
added by Jeff Garzik once this dependency (EXPORTS)
is resolved.
I know that's already in mainline but, man, that code is nasty. It has
stuff indented 7 levels or so and is
On Mon, 2008-02-11 at 10:49 +0100, Jan-Bernd Themann wrote:
are you the right person to address this patch to?
You might want to check the top of the file. ;)
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -52,11 +52,13 @@ int register_memory_notifier(struct notifier_block *nb)
On Tue, 2006-08-15 at 18:48 +0400, Andrey Savochkin wrote:
/* Can survive without statistics */
stats = kmalloc(sizeof(struct net_device_stats), GFP_KERNEL);
if (stats) {
memset(stats, 0, sizeof(struct net_device_stats));
-
On Wed, 2006-06-28 at 00:52 +0200, Herbert Poetzl wrote:
seriously, what I think Eric meant was that it
might be nice (especially for migration purposes)
to keep the device namespace completely virtualized
and not just isolated ...
It might be nice, but it is probably unneeded for an initial
I've noticed two oopses with a git tree I pulled yesterday. Last
commit: 4706df3d3c42af802597d82c8b1542c3d52eab23
Probably the same bug as the one that Andrew Morton forwarded here:
http://marc.theaimsgroup.com/?l=linux-netdevm=112618307911533w=2
I see a bunch of assertion failures, followed
.
-- Dave
Signed-off-by: Dave Hansen [EMAIL PROTECTED]
diff -ru linux-2.6-mm.orig/drivers/net/wireless/hostap/hostap.c
linux-2.6-mm/drivers/net/wireless/hostap/hostap.c
--- linux-2.6-mm.orig/drivers/net/wireless/hostap/hostap.c 2005-07-15
10:57:18.0 -0700
+++ linux-2.6-mm/drivers/net
19 matches
Mail list logo
