On Wed, Sep 09, 2015 at 10:14:46AM -0300, Emilio López wrote:
> On 09/09/15 01:12, Guenter Roeck wrote:
> >On 09/08/2015 08:58 PM, Greg KH wrote:
> >>On Tue, Sep 08, 2015 at 06:10:16PM -0700, Guenter Roeck wrote:
> >>>Hi Emilio,
> >>>
> >>>On 09/08/2015 05:51 PM, Emilio López wrote:
> Hi Greg
Re-ping. Can someone pull this into their tree?
-Kees
On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook wrote:
> This adds support for s390 to the seccomp selftests. Some improvements
> were made to enhance the accuracy of failure reporting, and additional
> tests were added to
On 09/09/2015 10:40 AM, Kees Cook wrote:
> Re-ping. Can someone pull this into their tree?
>
> -Kees
>
> On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook wrote:
>> This adds support for s390 to the seccomp selftests. Some improvements
>> were made to enhance the accuracy of
On Wed, 2015-09-09 at 12:36 -0400, Tejun Heo wrote:
> On Wed, Sep 09, 2015 at 09:33:52AM -0700, Joe Perches wrote:
> > On Wed, 2015-09-09 at 12:13 +0200, Maurizio Lombardi wrote:
> > > When printing a bitmap using the "%*pb[l]" printk format
> > > a 16 bit variable (field_width) is used to store
On Wed, Sep 09, 2015 at 06:43:11PM +1000, Michael Ellerman wrote:
> On Tue, 2015-09-08 at 16:34 +0200, Andrea Arcangeli wrote:
> >
> > I already had a few minor changes queued to be submitted for arm and
> > ppc and a few updates to the selftest.
> >
> > I didn't like that you had to remember
On Wed, Sep 9, 2015 at 9:56 AM, Shuah Khan wrote:
> On 09/09/2015 10:45 AM, Shuah Khan wrote:
>> On 09/09/2015 10:40 AM, Kees Cook wrote:
>>> Re-ping. Can someone pull this into their tree?
>>>
>>> -Kees
>>>
>>> On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook
On 09/09/2015 01:12 PM, santosh.shilim...@oracle.com wrote:
On 9/9/15 9:38 AM, Murali Karicheri wrote:
On 09/04/2015 11:53 PM, santosh.shilim...@oracle.com wrote:
On 9/4/15 5:46 PM, Murali Karicheri wrote:
To help the user, print the PDSP file name as part of
knav_queue_load_pdsp(). This will
On Wed, Sep 9, 2015 at 9:52 AM, Alexei Starovoitov
wrote:
> On Wed, Sep 09, 2015 at 09:37:51AM -0700, Kees Cook wrote:
>> On Wed, Sep 9, 2015 at 9:09 AM, Daniel Borkmann wrote:
>> > On 09/09/2015 06:07 PM, Alexei Starovoitov wrote:
>> >>
>> >>
On Wed, Sep 09, 2015 at 10:27:08AM -0700, Kees Cook wrote:
> On Wed, Sep 9, 2015 at 9:52 AM, Alexei Starovoitov
> wrote:
> > On Wed, Sep 09, 2015 at 09:37:51AM -0700, Kees Cook wrote:
> >> On Wed, Sep 9, 2015 at 9:09 AM, Daniel Borkmann
> >>
All make targets support $KCONFIG_CONFIG because they
run scripts/kconf. Make sure merge_config.sh accesses the
correct file in all cases.
Previously this script broke in two different code paths,
one for targets like kvmconfig (which use merge_config.sh -m
then call a target that respects
merge_config.sh can usefully be applied to a single file.
It implicitly merges with the default configuration.
Signed-off-by: Gabriel de Perthuis
Cc: Michal Marek
---
scripts/kconfig/merge_config.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Wed, Sep 09, 2015 at 06:10:22AM +0100, Eduardo Valentin wrote:
> Hi
Hi Eduardo,
> On Thu, Aug 27, 2015 at 11:55:49AM +0100, Javi Merino wrote:
> > From: Ørjan Eide
> >
> > Add a generic thermal cooling device for devfreq, that is similar to
> > cpu_cooling.
> >
> > The
Second attempt at this reply. The first reply was mangled.
On 9/8/2015 11:28 AM, David Daney wrote:
> From: David Daney
>
> It is perfectly legitimate for a PCI device to have an
> PCI_INTERRUPT_PIN value of zero. This happens if the device doesn't
> use interrupts, or
On 09/09/15 14:22, Jungseok Lee wrote:
> On Sep 9, 2015, at 1:47 AM, James Morse wrote:
>> On 08/09/15 15:54, Jungseok Lee wrote:
>>> On Sep 7, 2015, at 11:36 PM, James Morse wrote:
diff --git a/arch/arm64/kernel/irq.c b/arch/arm64/kernel/irq.c
index 463fa2e7e34c..10b57a006da8 100644
On Wed, 9 Sep 2015 18:27:31 +0800
Chen Yu wrote:
> In current code, max_perf_pct might be smaller than min_perf_pct
> by improper user input:
>
> $ grep . /sys/devices/system/cpu/intel_pstate/m*_perf_pct
> /sys/devices/system/cpu/intel_pstate/max_perf_pct:100
>
On Wednesday, September 09, 2015 11:20:25 AM Alan Stern wrote:
> On Wed, 9 Sep 2015, Rafael J. Wysocki wrote:
>
> > > The best example and actually the very specific problem we want to
> > > solve is handling touchscreens on a phone / tablet. When the screen is
> > > turned off, it is ideal to
On Wed, Sep 09, 2015 at 11:03:20PM +0300, Mike Rapoport wrote:
> On Wed, Sep 09, 2015 at 11:41:20AM -0700, Greg Kroah-Hartman wrote:
> > On Sun, Sep 06, 2015 at 09:17:56AM +0300, Mike Rapoport wrote:
> > > Fix the checkpatch warning about CamelCase.
> > >
> > > Signed-off-by: Mike Rapoport
On Wed, Sep 09, 2015 at 03:05:29PM -0400, Michael J Coss wrote:
> On 9/8/2015 11:54 PM, Greg KH wrote:
> > On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
> >> Currently when a uevent occurs, the event is replicated and sent to every
> >> listener on the kernel netlink socket,
On Wednesday 09 September 2015 12:30:27 Kees Cook wrote:
> The syscall ABI is inconsistent on aarch64 compat, so at least we should
> document it in the seccomp_bpf tests.
>
> Signed-off-by: Kees Cook
Can you explain in what way the ABI is inconsistent here?
> ---
> Can
On Wednesday, September 09, 2015 07:16:49 PM Suthikulpanit, Suravee wrote:
> Hi All,
>
> Are there any other concerns about this patch series?
I have none, but then it sort of missed the merge window.
I can easily queue it up for the next one unless it is super-urgent,
but in that case I need
On Wed, Sep 09, 2015 at 03:24:12PM -0400, Michael J Coss wrote:
> On 9/8/2015 11:55 PM, Greg KH wrote:
> > On Tue, Sep 08, 2015 at 10:10:29PM -0400, Michael J. Coss wrote:
> >> Adds capability to allow userspace programs to forward a given event to
> >> a specific network namespace as determined
Hi Patrick,
On 09/03/2015 02:18 AM, Patrick Bellasi wrote:
> In my view, one of the main goals of sched-DVFS is actually that to be
> a solid and generic replacement of different CPUFreq governors.
> Being driven by the scheduler, sched-DVFS can exploit information on
> CPU demand of active tasks
On Wed, Sep 9, 2015 at 1:35 PM, Rafael J. Wysocki wrote:
>
> On Wednesday, September 09, 2015 11:20:25 AM Alan Stern wrote:
> > On Wed, 9 Sep 2015, Rafael J. Wysocki wrote:
> >
> > > > The best example and actually the very specific problem we want to
> > > > solve is handling
On 9/9/2015 4:09 PM, Greg KH wrote:
> On Wed, Sep 09, 2015 at 03:05:29PM -0400, Michael J Coss wrote:
>> On 9/8/2015 11:54 PM, Greg KH wrote:
>>> On Tue, Sep 08, 2015 at 10:10:27PM -0400, Michael J. Coss wrote:
Currently when a uevent occurs, the event is replicated and sent to every
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It contains:
* New driver for NXP LPC18xx Watchdog Timer
* New driver for SAMA5D4 watchdog timer
* (nv_tco) add support for MCP79
* Clean-up and improvement of the mpc8xxx watchdog driver
*
On Wednesday, September 09, 2015 03:47:27 PM Lukasz Anaczkowski wrote:
> This series of patches attempts to fix how CPUs are enumerated by kernel when
> there's more than 255 of them on single processor.
> In such case, BIOS may interleave APIC/X2APIC MADT subtables, to obey
> requirements
>
On Wednesday 09 September 2015 17:44:54 Jon Hunter wrote:
>
> On 09/09/15 16:56, Arnd Bergmann wrote:
> > On Wednesday 09 September 2015 16:06:01 Jon Hunter wrote:
> >> +
> >> + idata = kcalloc(mcci.num_of_cmds, sizeof(*idata), GFP_KERNEL);
> >> + if (!idata) {
> >> +
This patch adds hot cpu support for Intel Cache allocation. Support
includes updating the cache bitmask MSRs IA32_L3_QOS_n when a new CPU
package comes online or goes offline. The IA32_L3_QOS_n MSRs are one per
Class of service on each CPU package. The new package's MSRs are
synchronized with the
This patch adds different APIs to manage the L3 cache capacity bitmask.
The capacity bit mask(CBM) needs to have only contiguous bits set. The
current implementation has a global CBM for each class of service id.
There are APIs added to update the CBM via MSR write to IA32_L3_MASK_n
on all
On Tue, Sep 08, 2015 at 09:14:01AM +0800, Boqun Feng wrote:
> Two examples for barriers in wake_up() and co. in memory-barriers.txt
> are misleading, along with their explanations:
>
> 1.The example which wanted to explain the write barrier in
> wake_up() and co. [spotted by Oleg
The syscall ABI is inconsistent on aarch64 compat, so at least we should
document it in the seccomp_bpf tests.
Signed-off-by: Kees Cook
---
Can someone with access to native aarch64 double-check this for me? I
think we need to change these tests to pass if it's expected,
On Wednesday, September 09, 2015 08:00:20 AM Viresh Kumar wrote:
> On 09-09-15, 03:06, Rafael J. Wysocki wrote:
> > I've just realized that if you combined this patch with the [6/9],
> > you wouldn't need to make any changes to gov_queue_work() at all,
> > because that patch removes the case in
From: Arnaldo Carvalho de Melo
Since we were not setting it to at least 3 chars ('CPU'), it was being
reset to zero when recalculating the columns width when refreshing the
screen, in 'perf top'. Fix it.
Cc: Adrian Hunter
Cc: Borislav Petkov
From: Arnaldo Carvalho de Melo
In ce80d3bef9ff ("perf tools: Rename perf_session_env to perf_env") we
forgot to rename a few functions to the "perf_env" prefix, do it now.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
From: Arnaldo Carvalho de Melo
Instead of reading
/sysfs/devices/system/cpu/cpu%d/topology/physical_package_id for
each sample.
While at it, check that the sample has PERF_SAMPLE_CPU, i.e. that
sample.cpu >= 0, to avoid an out of bounds access.
Reported-by: Wang Nan
Hi,
Please take a look at these changes to fix the problems reported by
Wang Nan wrt accesses to the cpu_topology_map information.
The fixes are present on these following two csets:
perf event: Use machine->env to find the cpu -> socket mapping
perf report: Do not blindly
On Sun, Sep 06, 2015 at 09:17:56AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase.
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_sii164.c | 2 +-
> drivers/staging/sm750fb/ddk750_swi2c.c | 2 +-
>
Hi,
On my system the kernel prints a stack trace and some error messages on
every boot, see below.
This is currently not causing any notable malfunction, but I wonder
what this is about. I tried bisecting the issue and endet up with this
commit as the first bad commit:
From: Arnaldo Carvalho de Melo
Out of the code to write the cpu topology map in the perf.data file
header.
Now if one needs the CPU topology map for the running machine, one needs
to call perf_env__read_cpu_topology_map(perf_env) and the info will be
stored in perf_env.cpu.
On 09/07/2015 09:32 AM, Sudeep Holla wrote:
> Hi Al,
>
> On 19/08/15 23:07, Al Stone wrote:
>
> I finally got a chance to try this series on Juno. Well it exposed a firmware
> bug in MADT table :)
>
> [..]
>
>> acpi_tbl_entry_handler handler,
>> @@ -245,6 +484,8 @@
- In cqm_pick_event_reader, use the existing package<->core map instead
of looping through all cpus in cqm_cpumask.
- In intel_cqm_cpu_exit, use the same map instead of looping through
all online cpus. In large systems with large number of cpus the time
taken to loop may be expensive and
There was a push back from cgroup maintainer Tejun on cgroup interface
usage during the previous version of patches. This patch series splits
the prior V13 patches to separate the cqos framework parts which just
provide APis to manage the closid/cbm management, scheduling, hot cpu etc
and the
On 9/8/2015 11:55 PM, Greg KH wrote:
> On Tue, Sep 08, 2015 at 10:10:29PM -0400, Michael J. Coss wrote:
>> Adds capability to allow userspace programs to forward a given event to
>> a specific network namespace as determined by the provided pid. In
>> addition, support for a per-namespace
Adds some data-structures and APIs to support Class of service
management(closid). There is a new clos_cbm table which keeps a 1:1
mapping between closid and capacity bit mask (cbm)
and a count of usage of closid. Each task would be associated with a
Closid at a time and this patch adds a new
Adds support for IA32_PQR_ASSOC MSR writes during task scheduling. For
Cache Allocation, MSR write would let the task fill in the cache
'subset' represented by the task's capacity bit mask.
The high 32 bits in the per processor MSR IA32_PQR_ASSOC represents the
CLOSid. During context switch
On Wed, 2015-09-09 at 20:51 +0200, Rasmus Villemoes wrote:
> On Wed, Sep 09 2015, Joe Perches wrote:
> > this makes the sizeof struct printf_spec more than
> > 8 bytes which isn't desireable on x86-32.
>
> I'm pretty sure struct printf_spec
> purposely has sizeof==8 to allow it
This patch is specific to Intel haswell (hsw) server SKUs. Cache
Allocation on hsw server needs to be enumerated separately as HSW does
not have support for CPUID enumeration for Cache Allocation. This patch
does a probe by writing a CLOSid (Class of service id) into high 32 bits
of IA32_PQR_MSR
Add documentation on using the cache allocation cgroup interface with
examples.
Signed-off-by: Vikas Shivappa
---
Documentation/cgroups/rdt.txt | 133 ++
1 file changed, 133 insertions(+)
create mode 100644
- In rapl_cpu_init, use the existing package<->core map instead of
looping through all cpus in rapl_cpumask.
- In rapl_cpu_exit, use the same mapping instead of looping all online
cpus. In large systems with large number of cpus the time taken to
loop may be expensive and also the time
Adds a new cgroup 'intel_rdt' to manage cache allocation. Each cgroup
directory is associated with a class of service id(closid). To map a
task with closid during scheduling, this patch removes the closid field
from task_struct and uses the already existing 'cgroups' field in
task_struct.
The
Adds a description of Cache allocation technology, overview of kernel
framework implementation. The framework has APIs to manage class of
service, capacity bitmask(CBM), scheduling support and other
architecture specific implementation. The APIs are used to build the
cgroup interface in later
This patch includes CPUID enumeration routines for Cache allocation and
new values to track resources to the cpuinfo_x86 structure.
Cache allocation provides a way for the Software (OS/VMM) to restrict
cache allocation to a defined 'subset' of cache which may be overlapping
with other 'subsets'.
Hi,
I've been trying the latest linus/master (a794b4f), which include this
patch, as baremetal kernel on X-gene. This is failing on early boot
without much log.
After bisecting the tree, I found the error coming from this patch.
While this patch is valid, it made me remembered that X-Gene (at
From: Sasha Levin
Date: Tue, 8 Sep 2015 10:53:40 -0400
> There was no verification that an underlying transport exists when creating
> a connection, this would cause dereferencing a NULL ptr.
>
> It might happen on sockets that weren't properly bound before attempting
David Drysdale writes:
> On Wed, Sep 9, 2015 at 1:25 AM, Eric W. Biederman
> wrote:
>> Andy Lutomirski writes:
>> > On Tue, Sep 8, 2015 at 4:07 PM, Eric W. Biederman
>> > wrote:
>>
>> >> Perhaps I had
b.zolnier...@samsung.com>
> >
> > What tree does this apply to?
>
> It applies fine to both next (next-20150909 branch) and current Linus'
> tree (top commit is a794b4f).
OK
My cpufreq branch has not acquired tegra20-cpufreq.c yet, so I'll apply this
one when -rc1 is
From: Arnaldo Carvalho de Melo
This reverts commit d49e4695077278ee3016cd242967de23072ec331.
We don't need it, using machine->env seems to be enough.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Frederic
From: Arnaldo Carvalho de Melo
Since it can be used separately from 'perf_session' and 'perf_header',
move it to separate include file and object, next csets will try to move
a perf_env__init() routine.
Cc: Adrian Hunter
Cc: Borislav Petkov
From: Arnaldo Carvalho de Melo
This reverts commit 2c07144dfce366e21465cc7b0ada9f0b6dc7b7ed.
We don't need it, machine->env provides what is needed.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Frederic
From: Arnaldo Carvalho de Melo
We have no use for it in evsel.h.
Cc: Adrian Hunter
Cc: Borislav Petkov
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Kan Liang
From: Arnaldo Carvalho de Melo
The 'struct machine' represents the machine where the samples were/are
being collected, and we also have a 'struct perf_env' with extra details
about such machine, that we were collecting at 'perf.data' creation time
but we also needed when no
From: Arnaldo Carvalho de Melo
Because it will require that we read the current machine CPU topology
map when the tool is not processing a perf.data file, from where it
would obtain that map.
Other tools may want to do some other initialization in such case.
We need to have a
From: Arnaldo Carvalho de Melo
We need to cache that info to use in perf_event__preprocess_sample(), so
that we don't read sysfs files for each sample.
The next patches will add machine->env pointer that will point to either
the perf_env read from a perf.data file header or
On Sun, Sep 06, 2015 at 09:17:51AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_hwi2c.c | 2 +-
> drivers/staging/sm750fb/ddk750_hwi2c.h | 2 +-
>
On Fri, Sep 04, 2015 at 06:53:18PM +0530, Sudip Mukherjee wrote:
> These variables were only assigned some values but they were never used.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging/slicoss/slicoss.c | 27 ++-
> 1 file changed, 6
On Sat, Sep 05, 2015 at 07:13:45PM +0530, Sudip Mukherjee wrote:
> Instead of defining DRVNAME and using it in all calls to pr_* family of
> macros lets start using pr_fmt.
>
> Signed-off-by: Sudip Mukherjee
> ---
> drivers/staging/fbtft/fbtft_device.c | 79
>
On Sun, Sep 06, 2015 at 09:17:53AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_hwi2c.c | 2 +-
> drivers/staging/sm750fb/ddk750_hwi2c.h | 2 +-
>
From: Arnaldo Carvalho de Melo
As al.cpu may be -1, i.e. no PERF_SAMPLE_CPU, and env->cpu may be NULL.
Rely instead on the work now done in perf_event__preprocess_sample(),
that does all those checks.
Reported-by: Wang Nan
Based-on-a-patch-by: Jiri Olsa
From: Arnaldo Carvalho de Melo
Move this from two globals to perf_env global, that eventually will
be just perf_header->env or something else, to ease the refactoring
series, leave it as a global and go on reading more of its fields,
not as part of the header writing process but
On Sun, Sep 06, 2015 at 09:17:52AM +0300, Mike Rapoport wrote:
> Fix the checkpatch warning about CamelCase
>
> Signed-off-by: Mike Rapoport
> ---
> drivers/staging/sm750fb/ddk750_hwi2c.c | 2 +-
> drivers/staging/sm750fb/ddk750_hwi2c.h | 2 +-
> 2 files changed, 2
On Wednesday, September 09, 2015 06:02:02 PM Octavian Purdila wrote:
> On Wed, Sep 9, 2015 at 4:55 PM, Oliver Neukum wrote:
> > On Wed, 2015-09-09 at 14:22 +0200, Rafael J. Wysocki wrote:
> >> > Note that when the screen is turned-on again, we want to resume the
> >> >
On Wed, Sep 09, 2015 at 11:41:20AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Sep 06, 2015 at 09:17:56AM +0300, Mike Rapoport wrote:
> > Fix the checkpatch warning about CamelCase.
> >
> > Signed-off-by: Mike Rapoport
> > ---
> > drivers/staging/sm750fb/ddk750_sii164.c
When working on the RISC-V port I noticed that F_SETLK64 was being
defined on our 64-bit platform, despite our port being so new that
we've only ever had the 64-bit file ops. Since there's not compat
layer for these, this causes fcntl to bail out.
It turns out that one of the ways in with
Nothing else in the kernel defines this, and this header is visible to
userspace. Rather than hiding it in an #ifdef, I think it's sane to
just make this visible to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
I cut the RISC-V stuff, but I intend to reply to it later. As you
said, it's just a different topic.
>>> However, I did see a lot of similar bugs now that you point me to it:
>>>
>>> $ grep -r \\\>> obj-tmp/usr/include/asm-generic/fcntl.h:#ifndef CONFIG_64BIT
>>>
I recently got bit by a CONFIG_ in userspace bug. This has apparently
happened before, but the check got disabled for triggering too much.
In order to reduce false positives, I added some hueristics to avoid
detecting comments.
Since these tests all pass, I've now re-enabled them.
I'm not sure what this is, but it doesn't feel like something that
should be exposed to userspace here. I'm assuming this file was
exposed for the structure in it, which doesn't depend on
MAX_SHARED_LIBS.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
I'm actually not sure what to do here: if this enum is meant to be
used by userspace, then it has to be the same regardless of kernel
configuration. One option would be to have the kernel expose all the
values to userspace and then map them internally if
CONFIG_HAVE_MIXED_BREAKPOINT_REGS isn't
Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity
check on the various subtables that are defined for the MADT. The check
compares the size of the subtable data structure as defined by ACPICA to
the length entry in the subtable. If they are not the same, the assumption
is
Now that we have introduced the bad_madt_entry() function, and that
function is being invoked in acpi_table_parse_madt() for us, there
is no longer any need to use the BAD_MADT_ENTRY macro.
Signed-off-by: Al Stone
Cc: Tony Luck
Cc: Fenghua Yu
Andi,
Andi Kleen [a...@firstfloor.org] wrote:
| From: Andi Kleen
|
| [This patch is on top of Sukadev's json patchkit]
I removed this line from the commit log...
|
| The JSON event lists use a different encoding for fixed counters
| than perf for instructions and cycles
Now that we have introduced to bad_madt_entry(), and we have removed
all the usages of the BAD_MADT_ENTRY macro from all of the various
architectures that use it (arm64, ia64, x86), we can remove the macro
definition since it is no longer used.
Signed-off-by: Al Stone
Cc:
Now that we have introduced the bad_madt_entry() function, and that
function is being invoked in acpi_table_parse_madt() for us, there
is no longer any need to use the BAD_MADT_ENTRY macro.
Signed-off-by: Al Stone
Cc: Rafael J. Wysocki
Cc: Len Brown
I don't think this was ever intended to be exposed to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/pktcdvd.h | 2 ++
1 file changed, 2 insertions(+)
The existing BAD_MADT_ENTRY macro only checks that the size of the data
structure for an MADT subtable matches the length entry in the subtable.
This is, unfortunately, not reliable. Nor, as it turns out, does it have
anything to do with what the length should be in any particular table.
We
I think this actually isn't a good idea, but I can't find anything
outside of the kernel that's using this so I'm going to hide it.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
On Sep 9 22:23, Francois Romieu wrote:
> Corinna Vinschen :
> [...]
> > diff --git a/drivers/net/ethernet/realtek/r8169.c
> > b/drivers/net/ethernet/realtek/r8169.c
> > index 24dcbe6..630811a 100644
> > --- a/drivers/net/ethernet/realtek/r8169.c
> > +++
I don't think this was ever meant to be exposed to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/raw.h | 2 ++
1 file changed, 2 insertions(+)
diff
Now that we have introduced the bad_madt_entry() function, and that
function is being invoked in acpi_table_parse_madt() for us, there
is no longer any need to use the BAD_MADT_ENTRY macro, or in the case
of arm64, the BAD_MADT_GICC_ENTRY, too.
Signed-off-by: Al Stone
This used to be hidden behind CONFIG_MMAP_ALLOW_UNINITIALIZED, so
userspace wouldn't actually ever see it. While I could have kept
hiding it, the man pages seem to indicate that MAP_UNINITIALIZED
should be visible:
mmap(2)
MAP_UNINITIALIZED (since Linux 2.6.33)
Don't clear anonymous
This doesn't make any sense to expose to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/eventpoll.h | 3 +++
1 file changed, 3 insertions(+)
diff --git
Michael Ellerman [m...@ellerman.id.au] wrote:
| > > This looks fine to me from an arch perspective. I assume the whole series
can
| > > go via tip-something?
| >
| > Yeah, I've had it queued for a few days, there was one s390 compile
| > fail reported by the build-bot, which I've just fixed. So
This one scares me: while I can't find any system calls that directly
take this as an argument, a comment in
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are also used in
the core dump). Please note that the
I think this change actually doesn't do anything: __NR_fork was still
being defined either way, and on my machine fork() in comes
from libc.
That said, I don't think there's any way to determine this
automatically, so this at least quiets the checker.
Signed-off-by: Palmer Dabbelt
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=104031
Fixes: 6e85d5ad36a26debc23a9a865c029cbe242b2dc8
Based on the discussion starting at
http://www.spinics.net/lists/netdev/msg342193.html
Tested locally on RTL8168evl/8111evl with various concurrent processes
accessing /proc/net/dev while
This used to just be behind an #ifdef COMPAT_COMPAT, so most of
userspace wouldn't have seen the definition before. This change just
makes the __KERNEL__ part explicit to quiet the header checker.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
DRA7 does use OPP, uses OMAP interconnect and also does require SCU.
These are missing in the SoC only build of DRA7 breaking various PM
features in DRA7 only build.
Reported-by: Carlos Hernandez
Signed-off-by: Nishanth Menon
---
arch/arm/mach-omap2/Kconfig |3 +++
When commit c4082d499fa2 ("ARM: omap2+: board-generic: clean up the
irq data from board file") cleaned up the direct usage of gic_of_init
and omap_intc_of_init, it failed to clean up the macros properly.
Since these macros are no longer used, lets just remove them.
Fixes: c4082d499fa2 ("ARM:
Den 09.09.2015 20:35, skrev Greg Kroah-Hartman:
On Sat, Sep 05, 2015 at 07:13:45PM +0530, Sudip Mukherjee wrote:
Instead of defining DRVNAME and using it in all calls to pr_* family of
macros lets start using pr_fmt.
Signed-off-by: Sudip Mukherjee
---
Hi,
While doing a SoC only build for DRA7, a few bugs did pop up. The
following series provides necessary fixups for the same.
Nishanth Menon (4):
ARM: OMAP4+: PM: erratum is used by OMAP5 and DRA7 as well
ARM: omap2+: board-generic: Remove stale of_irq macros
ARM: DRA7: Select missing
1301 - 1400 of 1422 matches
Mail list logo