Enhance HPET code to support hierarchy irqdomain, it helps to make
the architecture more clear.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/hpet.h |7 +-
arch/x86/kernel/apic/msi.c | 166 ++-
arch/x86/kernel/hpet.c | 57 ---
Now MSI interrupt has been converted to new hierarchy irqdomain
interfaces, so kill legacy MSI related code.
Signed-off-by: Jiang Liu
Acked-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 115 +
1 file changed, 2 insertions(+), 113 deletions(-)
Some irq_chip names use underscore, others use hyphen. So normalize them
to use hythen as separator.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/apic/msi.c b/arch/x86/kernel/apic/msi.c
index
Use common MSI interfaces to simplify DMAR/HPET driver implementation.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c | 192 +---
1 file changed, 54 insertions(+), 138 deletions(-)
diff --git a/arch/x86/kernel/apic/msi.c
Implement irq_chip.irq_write_msi_msg for MSI/DMAR/HPET irq_chips, they
will be used to share common code later.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c | 12
1 file changed, 12 insertions(+)
diff --git a/arch/x86/kernel/apic/msi.c b/arch/x86/kernel/apic/msi.c
Enhance UV code to support hierarchy irqdomain, it helps to make
the architecture more clear.
We should construct hwirq based on mmr_blade and mmr_offset, but
mmr_offset is type of unsigned long, it may exceed the range of
irq_hw_number_t. So help about the way to construct hwirq based
on
Function irq_chip_compose_msi_msg() can achieve the same goal as
msi_update_msg(), so kill msi_update_msg().
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
diff --git a/arch/x86/kernel/apic/msi.c
Simplify the way to deal with remapped MSI interrupts, so we could
kill irq_chip.irq_print_chip later.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c | 28
1 file changed, 24 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/apic/msi.c
Use hierarchy irqdomain to manage Hypertransport interrupts.
We have slightly changed the architecture interfaces to support htirq
PCI driver, it should be safe because currently Hypertransport interrupt
is only enabled on x86 platforms.
Signed-off-by: Jiang Liu
---
Now MSI interrupt has been converted to new hierarchy irqdomain
interfaces, so kill legacy MSI related code and interfaces.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/hpet.h |9 ---
arch/x86/include/asm/x86_init.h |4 ---
arch/x86/kernel/apic/msi.c | 55
Now MSI interrupt has been converted to new hierarchy irqdomain
interfaces, so kill legacy MSI related code.
Signed-off-by: Jiang Liu
Acked-by: Joerg Roedel
---
drivers/iommu/intel_irq_remapping.c | 144 ---
1 file changed, 144 deletions(-)
diff --git
Refine the interfaces to create IRQ for DMAR unit. It's a preparation
for converting DMAR IRQ to hierarchy irqdomain on x86.
It also moves dmar_alloc_hwirq()/dmar_free_hwirq() from irq_remapping.h
to dmar.h. They are not irq_remapping specific.
Signed-off-by: Jiang Liu
---
Now MSI interrupt has been converted to new hierarchy irqdomain
interfaces, so kill legacy MSI related code and interfaces.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/irq_remapping.h | 13 ---
arch/x86/include/asm/pci.h |5 --
arch/x86/kernel/x86_init.c |2 -
Enhance DMAR code to support hierarchy irqdomain, it helps to make
the architecture more clear.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/hw_irq.h |7 ++
arch/x86/kernel/apic/msi.c| 153 ++---
2 files changed, 103 insertions(+), 57
DMAR interrupt won't be remapped by interrupt remapping hardware,
so directly call native_compose_msi_msg() for DMAR IRQ to compose MSI
message data. This will help to simplify MSI code later.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c |6 ++
1 file changed, 2
Enhance MSI code to support hierarchy irqdomain, it helps to make
the architecture more clear.
Signed-off-by: Jiang Liu
---
arch/x86/Kconfig |1 +
arch/x86/include/asm/hw_irq.h|9 ++-
arch/x86/include/asm/irq_remapping.h |6 +-
arch/x86/include/asm/msi.h
Enhance AMD interrupt remapping driver to support hierarchy irqdomain,
it will simplify the code eventually.
Signed-off-by: Jiang Liu
Acked-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 329 ++-
drivers/iommu/amd_iommu_init.c |4 +
Prepare for support hierarchy irqdomain by changing function prototypes,
should be no function changes.
Signed-off-by: Jiang Liu
Acked-by: Joerg Roedel
---
drivers/iommu/intel_irq_remapping.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
Enhance Intel interrupt remapping driver to support hierarchy irqdomain,
it will simplify the code eventually. It also implements intel_ir_chip
to support stacked irq_chip.
Signed-off-by: Jiang Liu
Acked-by: Joerg Roedel
---
drivers/iommu/intel_irq_remapping.c | 337
Introduce new interfaces for interrupt remapping drivers to support
hierarchy irqdomain:
1) irq_remapping_get_ir_irq_domain(): get irqdomain associated with an
interrupt remapping unit. IOAPIC/HPET drivers use this interface to
get parent interrupt remapping irqdomain.
2)
Use new irqdomain interfaces to allocate/free IRQ for DMAR and interrupt
remapping, so we could kill GENERIC_IRQ_LEGACY_ALLOC_HWIRQ later.
The private definition of irq_alloc_hwirqs()/irq_free_hwirqs() are
temporary solution, it will be removed once we have converted interrupt
remapping driver to
Abstract CPU local APIC as an interrupt controller and create an
irqdomain for it to manage CPU interrupt vectors. It's the base to
enable hierarchy irqdomain on x86 systems. Eventually we will build
a irqdomain hierarchy as below:
IOAPIC domain---|
MSI/MSI-x domain--> [Inerrupt Remapping
Use new irqdomain interfaces to allocate/free IRQ for HTIRQ, so we could
kill GENERIC_IRQ_LEGACY_ALLOC_HWIRQ later.
This patch changes the interfaces between arch independent PCI driver
and arch specific code. Currently HT_IRQ is only enabled on x86, so it
shouldn't break other architectures.
Cache destination CPU APIC ID into struct irq_cfg when assigning vector
for interrupt. Upper layer just needs to read the cached APIC ID instead
of calling apic->cpu_mask_to_apicid_and(), it helps to hide APIC driver
details from IOAPIC/HPET/MSI drivers..
Signed-off-by: Jiang Liu
---
Use new irqdomain interfaces to allocate/free IRQ for HPET, so we could
kill GENERIC_IRQ_LEGACY_ALLOC_HWIRQ later.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/hpet.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
Use new irqdomain interfaces to allocate/free IRQ for PCI MSI, so we
could kill GENERIC_IRQ_LEGACY_ALLOC_HWIRQ later.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/msi.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kernel/apic/msi.c
We plan to restructure x86 interrupt code based on hierarchy irqdomain,
that is to build irqdomains for CPU vector, interrupt remapping unit,
IOAPIC, MSI and HPET etc and organize those irqdomains in hierarchy mode.
Each irqdomain manages corresponding interrupt controller and talks to
parent
Hi all,
Today's linux-next merge of the tip tree got a conflict in
drivers/acpi/processor_core.c between commit 9d48ea9f967b ("ACPI /
processor: Convert apic_id to phys_id to make it arch agnostic") from
the pm tree and commits 5922b6f497ed ("ACPI: Fix minor syntax issues in
processor_core.c")
Addy,
On Mon, Nov 24, 2014 at 6:38 PM, Addy wrote:
>> In worst case scenario, VDD = 3.6V and VIO = 2.7V. That gives as the
>> factor of 0.75, thus we are inside spec but without margins.
>
> * From eMMC4.5 spec:
> 1. (VDDF)vcc: Supply voltage for flash memory, which is 2.7v -- 3.3v
> 2.
On 11/24/2014 07:48 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Nov 21, 2014 at 03:23:13PM -0500, Josh Boyer wrote:
On Fri, Nov 21, 2014 at 3:16 PM, Andy Lutomirski wrote:
On Fri, Nov 21, 2014 at 12:14 PM, Josh Boyer wrote:
On Fri, Nov 21, 2014 at 2:52 PM, Andy Lutomirski wrote:
On Fri, Nov
On 11/22/2014 05:13 AM, Andrew Morton wrote:
> On Tue, 11 Nov 2014 10:56:30 +0530 Anshuman Khandual
> wrote:
>
>> This patch adds four new core note sections for PowerPC transactional
>> memory and one core note section for general miscellaneous debug registers.
>> These addition of new elf
Ulf,
On Mon, Nov 24, 2014 at 5:29 AM, Ulf Hansson wrote:
>> 2. Several people I've talked to have expressed concerns that our
>> minimum value is 2.7V. Apparently that's really on the edge and makes
>> EEs a little nervous. The quick sample of cards sitting on my desk
>> shows that they seem
> -Original Message-
> From: Dexuan Cui [mailto:de...@microsoft.com]
> Sent: Monday, November 24, 2014 8:33 PM
> To: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org; driverdev-
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com; KY
To force loading on Oracle Sun X86 servers, provide one kernel command line
parameter
intel_pstate = onora
For those who be aware of the risk doing so.
Signed-off-by: Ethan Zhao
---
v2: change to hardware vendor specific naming parameter.
Documentation/kernel-parameters.txt | 3 +++
Oracle Sun servers(X86) have power capping features that work via ACPI _PPC
method,
patch No.1 is used to skip this driver if Oracle Sun server and _PPC detected.
Patch No.2 introduces a kernel command line parameter for those who would like
to enable intel_pstate on Sun X86 servers and be aware
Oracle Sun X86 servers have dynamic power capping capability that works via
ACPI _PPC method etc, so skip loading this driver if Sun server has ACPI _PPC
enabled.
Signed-off-by: Ethan Zhao
---
v2: fix break HP Proliant issue.
v3: expand the hardware vendor list.
In commit 6067dc5a8c2b ("time: Avoid possible NTP adjustment mult
overflow") a new check was added to watch for adjustments that could
cause a mult overflow.
Unfortunately the check compares a signed with unsigned value and
ignored the case where the adjustment was negative, which causes
spurious
> -Original Message-
> From: Eric Auger [mailto:eric.au...@linaro.org]
> Sent: Monday, November 24, 2014 2:36 AM
> To: eric.au...@st.com; eric.au...@linaro.org; christoffer.d...@linaro.org;
> marc.zyng...@arm.com; linux-arm-ker...@lists.infradead.org;
> kvm...@lists.cs.columbia.edu;
On Mon, Nov 24, 2014 at 5:16 PM, pang.xunlei wrote:
> Ideally, __clocksource_updatefreq_scale, selects the largest shift
> value possible for a clocksource. This results in the mult memember
> of struct clocksource being particularly large, although not so large
> that NTP would adjust the clock
On Tue, 2014-11-25 at 00:35 +0100, Thomas Gleixner wrote:
> Aside of the general issues I have with this (see the inline replies
> to your changelog) the overall impression of this patch is that it is
> a half baken and carelessly cobbled together extract of some data base
> specific kernel
On 11/25/2014 07:20 AM, Heiko Stübner wrote:
Hi Chris,
Am Samstag, 15. November 2014, 19:45:07 schrieb Chris Zhong:
It's a basic version of suspend and resume for rockchip,
it only support RK3288 now.
please fold in both in the two patches from Doug
On 2014/11/24 22:51, Rafael J. Wysocki wrote:
> On Monday, November 24, 2014 07:03:54 PM Hanjun Guo wrote:
>> On 2014-11-24 9:27, Rafael J. Wysocki wrote:
>>> On Friday, October 17, 2014 09:36:58 PM Hanjun Guo wrote:
From: Ashwin Chaugule
The acpi_table_parse() function has a
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
drivers/net/wireless/iwlwifi/iwl-fw.h between commit 5ac6c72e5944
("iwlwifi: mvm: check TLV flag before trying to use hotspot firmware
commands") from the wireless tree and commit 77c5d7eff790 ("iwlwifi:
mvm: add TDLS
On 11/25/2014 12:32 PM, Dexuan Cui wrote:
> If num_ballooned is not 0, we shouldn't neglect the
> already-partially-allocated 2MB memory block(s).
>
> Cc: Jason Wang
> Cc: K. Y. Srinivasan
> Signed-off-by: Dexuan Cui
> ---
>
> v2: I fixed the logic error in v1, pointed by Jason Wang:
> In
If num_ballooned is not 0, we shouldn't neglect the
already-partially-allocated 2MB memory block(s).
Cc: Jason Wang
Cc: K. Y. Srinivasan
Signed-off-by: Dexuan Cui
---
v2: I fixed the logic error in v1, pointed by Jason Wang:
In v1: in the case of partially-allocated 2MB, alloc_error
On 2014/11/25 5:45, Alex Williamson wrote:
> On Sun, 2014-11-23 at 21:20 +0100, Thomas Gleixner wrote:
>> On Fri, 21 Nov 2014, Alex Williamson wrote:
>>> For the most part multivector MSI is not supported and drivers and
>>> hardware wanting multiple vectors opt for MSI-X instead. It seems
>>>
> -Original Message-
> From: Mitchel Humpherys [mailto:mitch...@codeaurora.org]
> Sent: Monday, November 24, 2014 7:21 PM
> To: Elliott, Robert (Server Storage)
...
> > The hpsa SCSI driver used to use usleep_range in a loop like
> > that, but we found that it caused scheduler problems
On Wed, Nov 05, 2014 at 04:49:36PM +0200, Kirill A. Shutemov wrote:
> FOLL_SPLIT is used only in two places: migration and s390.
>
> Let's replace it with explicit split and remove FOLL_SPLIT.
>
> Signed-off-by: Kirill A. Shutemov
> ---
...
> @@ -1246,6 +1246,11 @@ static int
When hardware supports APIC/x2APIC virtualization we don't need to use pirqs
for MSI handling and instead use APIC since most APIC accesses (MMIO or MSR)
will now be processed without VMEXITs.
As an example, netperf on the original code produces this profile
(collected wih 'xentrace -e 0x0008
Changes in v3:
* Explicitly include asm/apic.h in arch/x86/pci/xen.c for !CONFIG_SMP.
Changes in v2:
* New version of cpuid.h file from Xen tree (with a couple of style adjustments)
* Whitespace cleanup
Currently HVM guests handle MSI interrupts using pirqs/event channels, allowing
us to not
If the hardware supports APIC virtualization we may decide not to use pirqs
and instead use APIC/x2APIC directly, meaning that we don't want to set
x86_msi.setup_msi_irqs and x86_msi.teardown_msi_irq to Xen-specific routines.
However, x2APIC is not set up by the time pci_xen_hvm_init() is called
Here's a new update. I'll spare you the patch series and only show you
the rolled up patch. By swapping the parameters of
prepare_ftrace_return() that's used by ftrace_graph_caller, I was able
to have that take advantage of the rdi being filled for it too.
I pushed this up to my repo as well.
--
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/netfilter/nf_log.c between commit e71456ae9871 ("netfilter: Remove
checks of seq_printf() return values") from the vfs tree and commit
0c26ed1c07f1 ("netfilter: nf_log: Introduce nft_log_dereference()
macro") from the
On Sat, Nov 22, 2014 at 02:24:44AM -0500, David Miller wrote:
> From: Al Viro
> Date: Sat, 22 Nov 2014 04:28:57 +
>
> > OK, here's the next bunch. Sorry about the delay, iov_iter.c stuff
> > took most of the day (and it's not included in this pile). Please, review.
>
> I read over
On Fri, Nov 24, 2014 at 9:29 PM, Ulf Hansson
wrote:
On 21 November 2014 at 22:04, Doug Anderson wrote:
Hi,
On Fri, Nov 21, 2014 at 9:42 AM, Doug Anderson wrote:
Ulf,
On Fri, Nov 21, 2014 at 4:06 AM, Ulf Hansson wrote:
[...]
Sure
If the first card is sd2.0 since startup,
On Mon, 24 Nov 2014 17:34:04 -0800
Linus Torvalds wrote:
> On Mon, Nov 24, 2014 at 4:42 PM, Steven Rostedt wrote:
> >
> > Let me know if these changes have mcount.S give you less heebie-jeebies.
>
> So I haven't looked at the individual patches, I just looked at the
> rolled-up final patch in
Commit e25a64c4017e (and others in the same series) moved the locking
code to kernel/locking/. This patch just updates various docs and
comments (things like "see kernel/semaphore.c for documentation")
to refer to the new locations.
Signed-off-by: Jason Wilkes
---
Bug 86521 uncovered that some TOS6208 devices also return
non zero values on a write call to the backlight method,
thus getting caught and bailed out by the extra check code.
This patch changes the set_lcd_brightness function to its
"original" state by just adapting it to the new function
format.
On Mon, Nov 24, 2014 at 4:00 PM, Linus Torvalds
wrote:
> On Mon, Nov 24, 2014 at 2:58 PM, Alexei Starovoitov
> wrote:
>>
>> I've changed gcc pr58145-1.c reproducer to use
>> __read_once_size() approach above
>
> I don't think you did.
>
>> modified reproducer:
>> struct S { unsigned int data; };
Hi Vincent,
On 11/4/14, 12:54 AM, Vincent Guittot wrote:
The average running time of RT tasks is used to estimate the remaining compute
capacity for CFS tasks. This remaining capacity is the original capacity scaled
down by a factor (aka scale_rt_capacity). This estimation of available capacity
On 11/24/2014 09:00 AM, SF Markus Elfring wrote:
From: Markus Elfring
Date: Mon, 24 Nov 2014 17:34:23 +0100
Subject: [PATCH 0/6] Fix a few typos around the word "destroy"
The word "destroy" was mistyped in some files.
For all 6 patches;
Acked-by: Randy Dunlap
However, in th3 future, please
On Tue, 2014-11-25 at 00:35 +0100, Thomas Gleixner wrote:
> On Mon, 24 Nov 2014, Khalid Aziz wrote:
> > sched/fair: Add advisory flag for borrowing a timeslice
> >
> > This patch adds a way for a task to request to borrow one timeslice
> > from future if it is about to be preempted, so it could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/2014 03:56 PM, Khalid Aziz wrote:
> sched/fair: Add advisory flag for borrowing a timeslice
>
> This patch adds a way for a task to request to borrow one
> timeslice from future if it is about to be preempted, so it could
> delay preemption
On Mon, 24 Nov 2014 17:34:04 -0800
Linus Torvalds wrote:
> On Mon, Nov 24, 2014 at 4:42 PM, Steven Rostedt wrote:
> >
> > Let me know if these changes have mcount.S give you less heebie-jeebies.
>
> So I haven't looked at the individual patches, I just looked at the
> rolled-up final patch in
On Mon, Nov 24, 2014 at 5:52 PM, Andy Lutomirski wrote:
> I've tagged v3.5 of my paranoid stack code. It's in a strange state right
> now:
>
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/tag/?h=x86/paranoid=paranoid-stack-v3.5
--Andy
> Patch 1 (the actual stack switching) is
I've tagged v3.5 of my paranoid stack code. It's in a strange state right now:
Patch 1 (the actual stack switching) is standalone. It's not really a
good base for the memory failure stuff, because all of the ist_enter
stuff is missing. It should *work*, but the result will be ugly.
OTOH, it
(2014/11/25 0:19), Steven Rostedt wrote:
> On Mon, 24 Nov 2014 10:18:31 -0500
> Steven Rostedt wrote:
>
>> On Mon, 24 Nov 2014 10:07:27 -0500
>> Steven Rostedt wrote:
>>
>>> On Mon, 24 Nov 2014 23:11:12 +0900
>>> Masami Hiramatsu wrote:
>>>
So, if your server directory is mounted with
On Mon, Nov 17, 2014 at 12:23:33PM +, Lee Jones wrote:
> On Mon, 17 Nov 2014, gyun...@gmail.com wrote:
>
> > From: Gyungoh Yoo
> >
> > Signed-off-by: Gyungoh Yoo
> > ---
> > Changes v7:
> > Nothing
> >
> > Changes v6:
> > Nothing
> >
> > Changes v5:
> > Nothing
> >
> > Changes v4:
> >
Hi,
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Monday, November 24, 2014 11:20 PM
> Lv
> Subject: Re: [PATCH v3 updated 3/3] ACPI / PMIC: AXP288: support virtual GPIO
> in ACPI table
>
> On Monday, November 24, 2014 05:32:33 PM Aaron Lu wrote:
> > On 11/24/2014 09:06 AM,
Hi Dmitry,
> Add support for bluetooth MCI WB335 (AR9565) Wi-Fi+bt module.
> This bluetooth module requires loading patch and sysconfig by ath3k driver.
>
> CC: sta...@vger.kernel.org
> Signed-off-by: Dmitry Tunin
>
> ---
>
> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
Quoting Krzysztof Kozlowski (2014-11-24 07:18:31)
> For clocks depending on some other clock domain one may want to perform
> specific ops before actual enable/disable of gate clock. Allow such case
> by accepting supplied ops in new exported function:
> clk_register_gate_ops().
If you are not
On Mon, Nov 24, 2014 at 4:42 PM, Steven Rostedt wrote:
>
> Let me know if these changes have mcount.S give you less heebie-jeebies.
So I haven't looked at the individual patches, I just looked at the
rolled-up final patch in this email.
And yes, from that final patch, I certainly like this much
Hi Alan,
On Sat, Nov 22, 2014 at 7:55 AM, Alan Stern wrote:
> There is no USB wrapper for pm_runtime_idle calls, but one could be
> added. Still, in the meantime can you check to see what happens if you
> add
>
> pm_runtime_idle(>intf->dev);
>
> in usbhid_close() just after
On Friday, November 21, 2014 03:11:48 PM Aaron Lu wrote:
> v3:
> Only some function/variable name changes, no functiona changes:
> - Replace the dptf/DPTF word originate from the BIOS ACPI table with more
> meaningful word thermal/THERMAL in all places;
> - Eliminate the soc part in various
(2014/11/25 1:18), Shuah Khan wrote:
> On 11/24/2014 07:11 AM, Masami Hiramatsu wrote:
>> (CC'ed Shuah, since this is related to kselftest)
>>
>>
>> So, if your server directory is mounted with noexec, it's an environmental
>> problem. I guess you can not build any kernel drivers on that testbox,
On Mon, Nov 24 2014 at 04:53:19 PM, "Elliott, Robert (Server Storage)"
wrote:
>> -Original Message-
>> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
>> ow...@vger.kernel.org] On Behalf Of Mitchel Humpherys
>> Sent: Monday, 24 November, 2014 2:15 PM
> ...
>> From: Matt
On Thu, 20 Nov 2014 16:27:02 +0100 Jan Kara wrote:
> On Tue 18-11-14 03:37:19, Tejun Heo wrote:
> > Currently, a bdi (backing_dev_info) embeds single wb (bdi_writeback)
> > and the role of the separation is unclear. For cgroup support for
> > writeback IOs, a bdi will be updated to host
Em Mon, Nov 24, 2014 at 11:52:44PM +0100, Andi Kleen escreveu:
> > [root@zoo acme]# perf record -a -g -b sleep 2s
> > [ perf record: Captured and wrote 3.033 MB perf.data (~132504 samples) ]
> > [root@zoo acme]# perf report --stdio --branch-history
> > # To display the perf.data header info,
Ideally, __clocksource_updatefreq_scale, selects the largest shift
value possible for a clocksource. This results in the mult memember
of struct clocksource being particularly large, although not so large
that NTP would adjust the clock to cause it to overflow.
That said, nothing actually
On Mon, Nov 24, 2014 at 09:08:35PM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next full request for v3.19. I add detailed description of this
> pull request on below. Please pull extcon with following updates.
>
> This pull-request is based on Linux 3.18-rc3 (char-misc-next
On Mon, Nov 24, 2014 at 09:56:28PM +0100, Sebastian Andrzej Siewior wrote:
> On 11/24/2014 09:39 PM, Peter Stuge wrote:
> > Felipe Balbi wrote:
> A babble only occurs when
> the device side tries to move data without the host asking for anything.
> >>>
> >>> It also occurs if the device
create_new_namespaces() will be needed by call_usermodehelper_ns()
and call_usermodehelper_keys() for namespace restricted execution.
Signed-off-by: Ian Kent
Signed-off-by: Benjamin Coddington
Cc: Al Viro
Cc: J. Bruce Fields
Cc: David Howells
Cc: Trond Myklebust
Cc: Stanislav Kinsbursky
From: Benjamin Coddington
Copy the current task's namespaces into the request-key userspace helper to
restrict contained processes from executing key instantiation processes
outside their containers.
Signed-off-by: Benjamin Coddington
Signed-off-by: Ian Kent
Cc: Al Viro
Cc: J. Bruce Fields
The call_usermodehelper() function executes all binaries in the
global "init" root context. This doesn't allow a binary to be run
within the callers namespace (aka. a container). So create a new
function call_usermodehelper_ns() to do this.
Both containerized NFS client and NFS server need the
Some users of kmod.c's usermodehelper need to setup their fs_struct
root and pwd based on the callers namespaces after the kernel thread
runner has created a new process but before do_execve() is called.
Break out the fs_struct portion of mntns_install so it can be used
for this purpose.
Hi all,
Some time ago an attempt was made to update call_usermodehelper()
to execute within it's namespace.
Comments at the time were basically that the approach didn't go
nearly far enough to constrain the process.
This series attempts to remedy that by taking care to create an
appropriate
On 11/24/2014 11:50 PM, Jaewon Kim wrote:
> This patch adds support for haptic driver controlled by
> voltage of regulator. And this driver support for
> Force Feedback interface from input framework
>
> Signed-off-by: Jaewon Kim
> Signed-off-by: Hyunhee Kim
> Acked-by: Kyungmin Park
Looks
On 11/24/2014 11:50 PM, Jaewon Kim wrote:
> This patch adds regulator-haptic device node controlled by regulator.
>
> Signed-off-by: Jaewon Kim
> ---
> arch/arm/boot/dts/exynos3250-rinato.dts |7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git
Hi Oliver,
On Mon, Nov 24, 2014 at 1:13 AM, Oliver Neukum wrote:
>
> But there is very little to be gained by switching off remote wakeup.
> The additional energy consumption devices with remote wakeup enabled
> will be dwarfed by the energy needed for an additional wakeup.
>
That makes sense
On Mon, 2014-11-24 at 14:31 -0800, Sadasivan Shaiju wrote:
> HI,
>
> When using iperf with small buffers there is a performance
> degradation for 3.10 kernel from 2.6.32 kernel . Using
> profiling tools I am getting the following data.
>
> 2.6.32 kerne data
>
>
On Tuesday, November 25, 2014 08:18:34 AM Li, Aubrey wrote:
> On 2014/11/24 23:27, Rafael J. Wysocki wrote:
> > On Monday, November 24, 2014 10:39:55 AM Li, Aubrey wrote:
> >> On 2014/11/23 21:22, Lan Tianyu wrote:
> >>> ACPI 5.0 introduces _DEP to designate device objects that OSPM should
> >>>
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Mitchel Humpherys
> Sent: Monday, 24 November, 2014 2:15 PM
...
> From: Matt Wagantall
>
> It is sometimes necessary to poll a memory-mapped register until its
On Tue, Nov 25, 2014 at 12:00:59AM +0100, Pieter Smith wrote:
> REPO: https://github.com/smipi1/linux-tinification.git
>
> BRANCH: tiny/config-syscall-splice
>
> BACKGROUND: This patch-set forms part of the Linux Kernel Tinification effort
> (
> https://tiny.wiki.kernel.org/).
>
> GOAL:
On Tue, Nov 25, 2014 at 12:01:02AM +0100, Pieter Smith wrote:
> Many embedded systems will not need the splice-family syscalls (splice,
> vmsplice, tee and sendfile). Omitting them saves space. This adds a new
> EXPERT
> config option CONFIG_SYSCALL_SPLICE (default y) to support compiling them
The non-posix initializers are a holdover from Windows, where the compiler
doesn't have C99 initializers. We don't need that anymore, so the initializer
can indeed be uncommented.
Cheers, Andreas
> On Nov 24, 2014, at 16:41, Dan Carpenter wrote:
>
>> On Mon, Nov 24, 2014 at 07:55:41PM
Heiko,
在 2014年11月25日 07:39, Heiko Stübner 写道:
Hi Caesar,
Am Montag, 24. November 2014, 16:18:12 schrieb Eduardo Valentin:
Hello Caesar,
On Mon, Nov 24, 2014 at 12:58:57PM +0800, Caesar Wang wrote:
This series patchs tested on rk3288 SDK board and pinky-v1,v2 board.
I believe the driver can
Daniel Baluta schrieb am 18.11.2014 17:47:
> Minimal implementation for KMX61 6-axis accelerometer/magnetometer. It exports
> raw accel/magn readings together with scale and sampling frequency.
>
> Datasheet will be available at:
> http://www.kionix.com/6-axis-accelerometer-magnetometer/kmx61
>
From: "Steven Rostedt (Red Hat)"
Instead of having save_mcount_regs store the RIP in %rdx as a temp register
to place it in the proper location of the pt_regs on the stack. Use the
%rdi register as the temp register. This lets us remove the extra store
in the ftrace_caller_setup macro.
Link:
From: "Steven Rostedt (Red Hat)"
Linus pointed out that there were locations that did the hard coded
update of the parent and rip parameters. One of them was the static tracer
which could also use the ftrace_caller_setup to do that work. In fact,
because it did not use it, it is prone to bugs,
From: "Steven Rostedt (Red Hat)"
Currently save_mcount_regs is passed a "skip" parameter to know how much
stack updated the pt_regs, as it tries to keep the saved pt_regs in the
same location for all users. This is rather stupid, especially since the
part stored on the pt_regs has nothing to do
101 - 200 of 2022 matches
Mail list logo
