To easily set default config values into actual variables for 'colors' config,
it would be better that actual variables for each 'colors' config
also have only one value like 'default_config_item' type.
If we use combined {fore,back}ground colors values in ui_browser_colorset,
it smoothly work to
When initializing default perf config values,
we currently use values of actual type(int, bool, char *, etc.).
For example,
If there isn't user config value at ~/.perfconfig
for 'annotate.use_offset' config variable,
default value for it is 'true' bool type value in perf like below.
At ui/browser
Set default config values for 'colors' section with 'colors_config_items[]'
instead of actual const char * type values.
(e.g. using colors_config_item[CONFIG_COLORS_TOP].value.s
instead of "red, default" string value for 'colors.top')
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Wang
Set default config values for 'annotate' section with 'annotate_config_items[]'
instead of actual bool type values.
(e.g. using annotate_config_items[CONFIG_ANNOTATE_USE_OFFSET].value.b
instead of 'true' bool type value for 'annotate.use_offset'.)
Cc: Namhyung Kim
Cc: Jiri Olsa
Cc: Masami Hirama
* Dave Hansen wrote:
> On 07/11/2016 12:35 AM, Ingo Molnar wrote:
> > * Andy Lutomirski wrote:
> > mprotect_pkey()'s effects are per MM, but the system calls related to
> > managing the
> > keys (alloc/free/get/set) are fundamentally per CPU.
> >
> > Here's an example of how this could matte
Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@gmail.com]
> Subject: Re: [PATCH v2 4/4] ACPI / button: Add document for ACPI control
> method lid device restrictions
>
> On Fri, Jul 8, 2016 at 7:51 PM, Dmitry Torokhov
> wrote:
> > On Fri, Jul 08, 2016 at 11:17:39AM +0200, Benjamin Tis
Hi Arnd,
On 11/07/2016 at 23:42:57 +0200, Arnd Bergmann wrote :
> A cleanup patch introduced a harmless warning about now unused local
> variables:
>
> drivers/rtc/rtc-isl12057.c: In function 'isl12057_rtc_read_alarm':
> drivers/rtc/rtc-isl12057.c:249:26: error: unused variable 'alarm_secs'
> [
Actual variable for configs of 'annotate' section is like below.
(at ui/browsers/annoate.c)
static struct annotate_browser_opt {
bool hide_src_code,
use_offset,
jump_arrows,
show_linenr,
show_nr_jumps,
show_total_period;
} an
On 07/11/2016 09:47 PM, Chen Gang wrote:
On 7/11/16 08:26, Minchan Kim wrote:
On Sat, Jul 09, 2016 at 11:55:04PM +0800, cheng...@emindsoft.com.cn wrote:
From: Chen Gang
For pure bool function's return value, bool is a little better more or
less than int.
And return boolean result directly,
> From: linux-kernel-ow...@vger.kernel.org
> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Xunlei Pang
> Sent: Tuesday, July 12, 2016 3:57 PM
> On 2016/07/12 at 11:56, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > Hi Xunlei,
> >
> > Thanks for the review.
> >
> >> From: Xunlei Pang [mailto:xp...@red
On 2016年07月12日 12:30, Wan Zongshun wrote:
On 2016年07月12日 00:04, Arnd Bergmann wrote:
On Sunday, July 10, 2016 3:27:21 PM CEST Wan Zongshun wrote:
+ifeq ($(CONFIG_SOC_NUC970),)
obj-y := irq.o time.o mfp.o gpio.o clock.o
obj-y += clksel.o
On Mon 11-07-16 10:40:55, Shayan Pooya wrote:
> >
> > Could you post the stack trace of the hung oom victim? Also could you
> > post the full kernel log?
>
> Here is the stack of the process that lives (it is *not* the
> oom-victim) in a run with 100 processes and *without* strace:
>
> # cat /pro
On Mon 11-07-16 11:33:19, Shayan Pooya wrote:
> >> Could you post the stack trace of the hung oom victim? Also could you
> >> post the full kernel log?
>
> With strace, when running 500 concurrent mem-hog tasks on the same
> kernel, 33 of them failed with:
>
> strace: ../sysdeps/nptl/fork.c:136:
On Jul 11 2016 or thereabouts, Arnd Bergmann wrote:
> A recent commit added barry support to this driver, but that causes
> a link failure when CONFIG_POWER_SUPPLY is not set:
>
> drivers/hid/built-in.o: In function `hidpp_battery_get_property':
> :(.text+0x1a834): undefined reference to `power_su
On 2016/07/12 at 15:12, 河合英宏 / KAWAI，HIDEHIRO wrote:
>> From: linux-kernel-ow...@vger.kernel.org
>> [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Xunlei Pang
>> Sent: Tuesday, July 12, 2016 3:57 PM
>> On 2016/07/12 at 11:56, 河合英宏 / KAWAI，HIDEHIRO wrote:
>>> Hi Xunlei,
>>>
>>> Thanks for
On 2016年07月11日 23:36, Arnd Bergmann wrote:
On Sunday, July 10, 2016 3:27:23 PM CEST Wan Zongshun wrote:
+config NUC900_TIMER
+bool "Clocksource timer for nuc900 platform" if COMPILE_TEST
+depends on ARM
+select CLKSRC_OF if OF
+select CLKSRC_MMIO
+help
Hi,
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Benjamin Tissoires
> Subject: Re: [PATCH v2 4/4] ACPI / button: Add document for ACPI control
> method lid device restrictions
>
> [I just realised Ctrl+enter means "send" for gmail, see the end
Hi, Dmitry
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Subject: Re: [PATCH v2 4/4] ACPI / button: Add document for ACPI control
> method lid device restrictions
>
> On Mon, Jul 11, 2016 at 01:34:08PM +0200, Benjamin Tissoires wrote:
> > On Fri, Jul 8, 2016 at 7:51 PM, Dmitry Toro
On Tue 12-07-16 03:47:42, Chen Gang wrote:
[...]
> In our case, the 2 output size are same, but under x86_64, the insns are
> different. After uses bool, it uses push/pop instead of branch, for me,
> it should be a little better for catching.
The code generated for bool version looks much worse. L
On 12/07/16 02:36, Bin Wu wrote:
> During scsi command queueing or exception handling, if prepairing
> fails, we need to reclaim the failed request. Otherwise, the garbage
> request will be pushed into the ring for the backend to work.
>
> Signed-off-by: Bin Wu
Reviewed-by: Juergen Gross
> ---
Hello Mike...
It (at least) seems like that the fact that this is a Intel Rapid
Storage RAID10 does play a role after all.
I did several tests this morning, after I finally managed to get
another disk hooked up via USB3 (the best I could do for now).
I tried dm-crypt w/ a single partition and w
Hi Shanker,
On 12/07/16 04:36, Shanker Donthineni wrote:
> Read-allocation hints are not enabled for both the GIC-ITS and GICR
> tables. This forces the hardware to always read the table contents
> from an external memory (DDR) which is slow compared to cache memory.
> Most of the tables are often
On Mon, Jul 11, 2016 at 11:54:52AM -0400, Steven Rostedt wrote:
> On Sun, 10 Jul 2016 13:08:02 +0200
> Jiri Olsa wrote:
>
> > Jirka reported that python code returns all arrays as strings.
> > This makes impossible to get all items for byte array tracepoint
> > field containing 0x00 value item.
>
On Mon, 2016-07-11 at 22:49 +0200, Arnd Bergmann wrote:
> The iwl-debug.h header relies in implicit inclusion of linux/device.h
> and
> we get a lot of warnings without that:
>
> drivers/net/wireless/intel/iwlwifi/iwl-debug.h:44:23: error: 'struct
> device' declared inside parameter list will not
On Mon, Jul 11, 2016 at 10:56 AM, tiffany lin wrote:
> Hi Hans,
>
> On Fri, 2016-07-08 at 12:23 +0200, Hans Verkuil wrote:
>> On 05/30/2016 02:29 PM, Tiffany Lin wrote:
>> > Add V4L2_PIX_FMT_MT21 documentation
>> >
>> > Signed-off-by: Tiffany Lin
>> > ---
>> > Documentation/DocBook/media/v4l/pix
On Tuesday, July 12, 2016 3:14:47 PM CEST Wan Zongshun wrote:
> On 2016年07月12日 12:30, Wan Zongshun wrote:
> >
> >
> > On 2016年07月12日 00:04, Arnd Bergmann wrote:
> >> On Sunday, July 10, 2016 3:27:21 PM CEST Wan Zongshun wrote:
> >>> +ifeq ($(CONFIG_SOC_NUC970),)
> >>> obj-y
On 12/07/16 05:34, James Liao wrote:
Hi Matthias,
On Mon, 2016-07-11 at 15:10 +0200, Matthias Brugger wrote:
On 11/07/16 10:56, James Liao wrote:
[...]
@@ -467,28 +386,54 @@ static int scpsys_probe(struct platform_device *pdev)
if (PTR_ERR(scpd->supply) == -ENODEV)
On 07/12/16 at 02:52pm, Xunlei Pang wrote:
> On 2016/07/07 at 18:17, Wei Jiangang wrote:
> > Signed-off-by: Wei Jiangang
> > ---
> > +/* Local APIC is disabled by the kernel for crash or reboot path */
> > +static int disabled_local_apic;
> > +
> > /*
> > * Knob to control our willingness to en
On Tuesday, July 12, 2016 3:04:42 PM CEST Wan Zongshun wrote:
> >
> > Ideally, this should just go away once we use SPARSE_IRQ.
>
> This platform also can use SPARSE_IRQ? this just a simple irq map and no
> more irq number in this Soc.
>
SPARSE_IRQ is implied by ARCH_MULTIPLATFORM, so we will h
Kindly permit me to crave your indulgence by introducing a project that might
have something to do with you or a member of your immediate or extended family.
I am Sergei Malyukov, I am the Director heading the accounting and audit
department of the PJSC LUKOIL Moscow Russia. You can check out my
Hi,
On Mon, Jul 11, 2016 at 3:33 AM, Peter Zijlstra wrote:
> On Sun, Jul 10, 2016 at 11:48:11AM -0700, Stephane Eranian wrote:
>> So we either redirect ref-cycles towards 0x013c
>> (cpu_clk_unhalted:xlck) or another event maybe
>
> Another solution is us introducing (another) fake event, say 0x04
On Tuesday, July 12, 2016 3:32:59 PM CEST Wan Zongshun wrote:
>
> On 2016年07月11日 23:36, Arnd Bergmann wrote:
> > On Sunday, July 10, 2016 3:27:23 PM CEST Wan Zongshun wrote:
> >>
> >> +config NUC900_TIMER
> >> +bool "Clocksource timer for nuc900 platform" if COMPILE_TEST
> >> +depe
On Tuesday, July 12, 2016 6:57:10 AM CEST Bharat Kumar Gogada wrote:
> Hi,
>
> I have a query.
>
> Can any once explain the purpose of pci_remap_iospace function in root port
> driver.
>
> What is its dependency with architecture ?
>
> Here is my understanding, the above API takes PCIe IO reso
Hello,
I posted this issue already on linux-mm, linux-kernel and dm-devel a
few days ago and after further investigation it seems like that this
issue is somehow related to the fact that I am using an Intel Rapid
Storage RAID10, so I am summarizing everything again in this mail
and include linux-
On Tuesday, July 12, 2016 10:42:24 AM CEST Dongdong Liu wrote:
> MAINTAINERS | 1 +
> drivers/pci/host/Kconfig | 7 ++
> drivers/pci/host/Makefile | 1 +
> drivers/pci/host/mcfg-quirks.c| 8 ++
> drivers/pci/host/mcfg-quirks.h| 8 ++
> drive
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Monday, July 11, 2016 12:14 PM
> To: Rajesh Bhagat
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> devicet...@vger.kernel.org; Peter Chen ;
> gre...@linuxfoundation.org; kis...@ti.com; robh...
On Tue, Jul 12, 2016 at 02:32:45PM +0800, Hillf Danton wrote:
> > > To avoid excessive reclaim, we give up rebalancing for high order
> > > allocations right after reclaiming enough pages.
> >
> > hm. What are the observed runtime effects of this change? Any testing
> > results?
> >
> This work
On Mon, Jul 11, 2016 at 11:28:07AM -0700, Yeshaswi M R Gowda wrote:
>
> + u_ctx = ULD_CTX(ctx);
> + if (cxgb4_is_crypto_q_full(u_ctx->lldi.ports[0], ctx->tx_channel_id))
> + return -EBUSY;
You cannot just return -EBUSY. If the request has the MAY_BACKLOG
bit set, it must be qu
> Subject: Re: Purpose of pci_remap_iospace
>
> On Tuesday, July 12, 2016 6:57:10 AM CEST Bharat Kumar Gogada wrote:
> > Hi,
> >
> > I have a query.
> >
> > Can any once explain the purpose of pci_remap_iospace function in root
> port driver.
> >
> > What is its dependency with architecture ?
> >
>
On 11/07/16 16:16, Xunlei Pang wrote:
> On 2016/07/11 at 16:01, luca abeni wrote:
> > Hello,
> >
> > On Mon, 11 Jul 2016 13:03:56 +0800
> > Xunlei Pang wrote:
> >
> >> On 2016/07/08 at 19:28, Juri Lelli wrote:
> > [...]
> >>> @@ -363,6 +364,15 @@ static inline void setup_new_dl_entity(struct
> >>>
On Tue, Jul 12, 2016 at 03:30:41AM +0800, kbuild test robot wrote:
> Hi,
>
> [auto build test WARNING on net-next/master]
> [also build test WARNING on v4.7-rc7 next-20160711]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
Yeshaswi, please
Op 11-07-16 om 22:27 schreef Gustavo Padovan:
> 2016-07-10 Maarten Lankhorst :
>
>> Op 08-07-16 om 17:44 schreef Gustavo Padovan:
>>> From: Gustavo Padovan
>>>
>>> Signalling doesn't need to be enabled at sync_file creation, it is only
>>> required if userspace waiting the fence to signal through
On Monday, July 11, 2016 3:00:13 PM CEST Michael Turquette wrote:
> Quoting Arnd Bergmann (2016-07-11 13:21:17)
> > On Thursday, July 7, 2016 7:10:30 PM CEST Michael Turquette wrote:
> > > Quoting Arnd Bergmann (2016-07-07 01:13:58)
> > > > On Wednesday, July 6, 2016 5:19:53 PM CEST Michael Turquet
On 07/11/2016 04:44 PM, Abhilash Kesavan wrote:
> Hi Krzysztof,
>
> [...]
>>> diff --git a/drivers/soc/samsung/exynos-pmu.c
>>> b/drivers/soc/samsung/exynos-pmu.c
>>> index 0acdfd8..7cda8fb 100644
>>> --- a/drivers/soc/samsung/exynos-pmu.c
>>> +++ b/drivers/soc/samsung/exynos-pmu.c
>>> @@ -88,6 +
> This decision
> was based on the fact the series did not appear to be over-reclaiming for
> high-order pages when compared with zone-lru.
>
Then dropped.
thanks
Hillf
On 07/11/2016 04:44 PM, Abhilash Kesavan wrote:
> Hi Krzysztof,
>
> On Wed, Jul 6, 2016 at 8:47 AM, Krzysztof Kozlowski
> wrote:
>> On Tue, Jul 5, 2016 at 10:28 PM, Abhilash Kesavan
>> wrote:
>>> Exynos7 has certain PMU registers that needs to be configured with
>>> u32 values.
>>>
>>> Signed-o
On Mon, 11 Jul 2016, Mark Hounschell wrote:
> Well, all that was specified in my original post. I can no longer open the
> floppy drive with no floppy media inserted. Worse, I can also no longer open a
> floppy with media inserted that is not a "linux" recognized format. A floppy
> drive is a remo
On 07/11/16 21:57, Eric W. Biederman wrote:
> Topi Miettinen writes:
>
>> There are many basic ways to control processes, including capabilities,
>> cgroups and resource limits. However, there are far fewer ways to find
>> out useful values for the limits, except blind trial and error.
>>
>> Curr
Andy Lutomirski wrote:
>
> Known issues: - tcp md5, rxkad, virtio_net, and virtio_console will
> have issues. Eric Dumazet has a patch for tcp md5, and Michael
> Tsirkin says he'll fix virtio_net and virtio_console. rxkad will be
> fixed via net-next.
There is one more stack SG user within cryp
On 07/11/2016 06:38 PM, Sylwester Nawrocki wrote:
> On 07/11/2016 04:44 PM, Abhilash Kesavan wrote:
+ /*
>> +* Set clock freeze cycle count to 0 before and after arm clamp
>> or
>> +* reset signal transition
>> +*/
>> + node = of_find_co
Hi Matthias,
On Fri, 2016-07-08 at 14:47 +0200, Matthias Brugger wrote:
>
> On 06/07/16 07:22, James Liao wrote:
> > On Sat, 2016-07-02 at 18:35 +0200, Matthias Brugger wrote:
> >>
> >> On 05/16/2016 11:28 AM, James Liao wrote:
> >>> Some power domain comsumers may init before module_init.
> >>>
The patch
regulator: s2mps11: Fix the voltage linear range for s2mps15
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
Some gadget device (such as dwc3 gadget) requires quirk_ep_out_aligned_size
attribute, which means it need to align the request buffer's size to an ep's
maxpacketsize.
Thus we add usb_ep_align_maybe() function to check if it is need to align
the request buffer's size to an ep's maxpacketsize.
Sig
The patch
regulator: qcom_smd: Avoid overlapping linear voltage ranges
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On 2016年07月08日 19:44, Joerg Roedel wrote:
Hi,
here is a patch-set to make the AMD IOMMU driver use the
generic IOVA allocator, which is already used in the Intel
VT-d driver and a few other places.
The main reason for the conversion is to make the driver
benefit from the recent scalability im
Hi Peter,
have you a chance to look into this? Is there anything I can do to
help you to fix it?
Thanks a lot!
Jirka
On Wed, Jun 29, 2016 at 11:58 AM, Peter Zijlstra wrote:
> On Wed, Jun 29, 2016 at 11:47:56AM +0200, Jirka Hladky wrote:
>> Hi Peter,
>>
>> I think Cluster on Die technology was
On 2016年07月11日 16:03, Arnd Bergmann wrote:
On Sunday, July 10, 2016 3:27:26 PM CEST Wan Zongshun wrote:
+ ret = of_property_read_string(np, "compatible", &soc_dev_attr->soc_id);
+ if (ret)
return -EINVAL;
+
+ soc_dev_attr->machine = "NUC900EVB";
+ soc_dev
On 29/06/16 20:49, Markus Mayer wrote:
From: Florian Fainelli
Add an ARCH_BRCMSTB Kconfig symbol which allows us not to update the
dependencies for all STB-related drivers. Select BRCMSTB_L2_IRQ and
GENERIC_IRQ_CHIP which are required for proper functioning.
Signed-off-by: Doug Berger
Signe
On Tue, 2016-07-12 at 14:52 +0800, Xunlei Pang wrote:
> On 2016/07/07 at 18:17, Wei Jiangang wrote:
> > If we specify the 'notsc' boot parameter for the dump-capture kernel,
> > and then trigger a crash(panic) by using "ALT-SysRq-c" or "echo c >
> > /proc/sysrq-trigger",
> > the dump-capture kernel
On Tue, 2016-07-12 at 16:21 +0800, Baoquan He wrote:
> On 07/12/16 at 02:52pm, Xunlei Pang wrote:
> > On 2016/07/07 at 18:17, Wei Jiangang wrote:
> > > Signed-off-by: Wei Jiangang
> > > ---
> > > +/* Local APIC is disabled by the kernel for crash or reboot path */
> > > +static int disabled_local_
> Subject: Re: PCIe MSI address is not written at pci_enable_msi_range call
>
> On 11/07/16 11:51, Bharat Kumar Gogada wrote:
> >>> Hi Marc,
> >>>
> >>> Thanks for the reply.
> >>>
> >>> From PCIe Spec:
> >>> MSI Enable Bit:
> >>> If 1 and the MSI-X Enable bit in the MSI-X Message Control register
On Mon, Jul 11, 2016 at 12:43:41PM +0200, Alexander Gordeev wrote:
> > I diagreed - if we deprecated functions the only thing that should
> > be mentioned is a "don't use these".
>
> I will try to paraphrase myself. The new API deprecates pci_enable_msi*_range
> functions, but I am not that sure
On Tue, 12 Jul 2016, Benjamin Tissoires wrote:
> > A recent commit added barry support to this driver, but that causes
> > a link failure when CONFIG_POWER_SUPPLY is not set:
> >
> > drivers/hid/built-in.o: In function `hidpp_battery_get_property':
> > :(.text+0x1a834): undefined reference to `po
Set the affinity_mask in the PCI device before allocating vectors so that
the affinity can be propagated through the MSI descriptor structures to
the core IRQ code. To facilitate this new __pci_enable_msi_range and
__pci_enable_msix_range helpers are factored out of their not prefixed
variants whi
To factor out the calculation of the base address for a given MSI-X vector.
Signed-off-by: Christoph Hellwig
---
drivers/pci/msi.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index a080f44..0d94fbf 100644
--- a/drive
Instead of relying on the msix_entry structure for the vector number read
it from the msi_desc.
Signed-off-by: Christoph Hellwig
---
drivers/pci/msi.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index 0d94fbf..a385f39 100644
---
The entries argument isn't needed if the list of entries does not
contain any holes. Make it optional so that we can the need for
having to allocate a msix_entry structure for this (common) case.
Signed-off-by: Christoph Hellwig
Reviewed-by: Alexander Gordeev
---
drivers/pci/msi.c | 30 +++
This series adds a new set of functions that transparently use the right
type of interrupt (MSI-X, MSI, legacy interrupt line) for a PCI device,
and if multiple vectors are supported automatically spreads the irq
routing to different CPUs. This will allow the block layer (and hopefully
other consu
Add a function to allocate and free a range of interrupt vectors, using
MSI-X, MSI or legacy vectors (in that order) based on the capabilities
of the underlying device and PCIe complex.
Additionally a new helper is provided to get the Linux IRQ number for
given device-relative vector so that the d
On Monday 27 June 2016 09:20 PM, Peter Zijlstra wrote:
> On Tue, Jun 14, 2016 at 10:19:51PM +0530, Aravinda Prasad wrote:
>> Whenever perf tool is executed inside a container, this
>> patch restricts the events to the perf-namespace in which
>> the perf tool is executing.
>>
>> This patch is base
Good day,
I am Bun Sam. I work with one of the major banks in Cambodia as the director of
audit. I have a proposal for you, a very urgent and quick business that will be
completed in 12 working days. I have just discovered documents relating to
funds belonging to a deceased client of our bank,
Hi guys!
If I compile kernel 4.6.4 (and some older one), I always get the message
"Warning: CONFIGURE-FSTACK-PROTECTION not supported by the compiler." I
wonder because I use the newest (6.1.0) gcc compiler!
benny
On Jul 08 2016 or thereabouts, Aaron Armstrong Skomra wrote:
> On Tue, Jul 5, 2016 at 7:39 AM, Benjamin Tissoires <
> benjamin.tissoi...@redhat.com> wrote:
>
> > Or Gnome complains about an empty battery.
> >
> > Hi Benjamin,
>
> I tested this series on the 24HD, 21UX2, Intuos P&T (CTH-680), and
On 07/12/16 at 09:09am, Wei, Jiangang wrote:
> On Tue, 2016-07-12 at 14:52 +0800, Xunlei Pang wrote:
> > On 2016/07/07 at 18:17, Wei Jiangang wrote:
> > > diff --git a/arch/x86/kernel/machine_kexec_32.c
> > > b/arch/x86/kernel/machine_kexec_32.c
> > > index 469b23d6acc2..c934a7868e6b 100644
> > >
From: Colin Ian King
The result of mb86a20s_readreg(state, 0x0a) & 0xf is always in the range
0x00 to 0x0f and can never be negative, so remove the redundant check
of the result being less than zero.
Signed-off-by: Colin Ian King
---
drivers/media/dvb-frontends/mb86a20s.c | 2 --
1 file change
Ciao
Sei disperato bisogno di un prestito?
Sei stato negato di un prestito dalla propria banca o qualsiasi istituzione?
Avete bisogno di assistenza finanziaria?
Avete bisogno di un prestito per pagare le bollette o acquistare una casa?
Vuoi avere un business di tuo e hai bisogno di un prestito per
add Hisilicon BVT I2C controller driver support.
Signed-off-by: Pan Wen
---
change log
v2:
1)Fixed a compile error.
2)Dropped the clock-names property.
.../devicetree/bindings/i2c/i2c-hibvt.txt | 23 +
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makef
On 11/07/16 19:00, Nate Watterson wrote:
> In the current arm-smmu-v3 driver, all smmus that support 2-level
> stream tables are being forced to use them. This is suboptimal for
> smmus that support fewer stream id bits than would fill in a single
> second level table. This patch limits the use of
Hello,
On (07/11/16 15:35), Viresh Kumar wrote:
[..]
> Sometimes, the platform doesn't come back after suspend. I have tried
> enabling no-console-suspend and the last line it prints is:
>
> Disabling non-boot CPUs
>
> And nothing after that at all. We have to forcefully reboot the phone
The failure of create debugfs of VM will return directly without release
the anon file. It will leak memory and file descriptors, even through
be not serious.
Signed-off-by: Liu Shuo
---
virt/kvm/kvm_main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_
On Mon, Jul 11, 2016 at 01:17:09PM -0700, Andrew Morton wrote:
> On Mon, 11 Jul 2016 12:47:36 +0530 akash.g...@intel.com wrote:
>
> > From: Akash Goel
> >
> > The following patch added support to use channels with no associated files.
> > relay: add buffer-only channels; useful for early log
The _scsih_pci_mmio_enabled called if scsih_pci_error_detected returns
PCI_ERS_RESULT_CAN_RECOVER, at this point, read/write to the device
still works, no need to reset slot.
Or the mpt3sas_base_map_resources in scsih_pci_slot_reset will fail,
and iounamp ioc->chip, then we will meet issue when re
Read data fails sometimes because of a timeout that PMIC cannot transfer data
to PMIC wrap on time, extend the wainting time to 10ms to reduce the failed
rate.
Signed-off-by: Henry Chen
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/d
On Mon, 11 Jul 2016, Jessica Yu wrote:
> +++ Miroslav Benes [11/07/16 16:03 +0200]:
> > On Mon, 27 Jun 2016, Torsten Duwe wrote:
> >
> > > diff --git a/arch/arm64/include/asm/livepatch.h
> > > b/arch/arm64/include/asm/livepatch.h
> > > new file mode 100644
> > > index 000..6b9a3d1
> > > --- /
On Tue 12-07-16 10:27:37, Matthias Dahl wrote:
> Hello,
>
> I posted this issue already on linux-mm, linux-kernel and dm-devel a
> few days ago and after further investigation it seems like that this
> issue is somehow related to the fact that I am using an Intel Rapid
> Storage RAID10, so I am su
On Tuesday, July 12, 2016 5:06:10 PM CEST Wan Zongshun wrote:
> On 2016年07月11日 16:03, Arnd Bergmann wrote:
> > On Sunday, July 10, 2016 3:27:26 PM CEST Wan Zongshun wrote:
> > I'm still a bit unsure about the set of attributes here.
> >
> > - The "soc_id" is read from the device tree from the field
On 6 July 2016 at 18:21, Ulf Hansson wrote:
> On 4 July 2016 at 13:56, Bojan Prtvar wrote:
>> Make operation conditions register (OCR) easily accessible from user space.
>>
>> Signed-off-by: Bojan Prtvar
>
> Thanks, applied for next! Amended the changelog with the explanation
> why this change i
On 05/07/2016 17:28, Florian Fainelli wrote:
> Le 05/07/2016 07:50, Mason wrote:
>
>> On 05/07/2016 15:33, Mason wrote:
>>
>>> I was testing suspend/resume sequences where the suspend operation
>>> fails and returns without having suspended the platform.
Please forget I ever mentioned suspend,
From: Arnaldo Carvalho de Melo
evsel->overwrite indicator means an event should be put into
overwritable ring buffer. In current implementation, it equals to
evsel->attr.write_backward. To reduce compliexity, remove
evsel->overwrite, use evsel->attr.write_backward instead.
In addition, in __perf
Add a 'ptr' field to fdarray->priv array.
This feature will be used by following commits, which introduce muiltiple
'struct perf_mmap' array for different types of mapping. Because of this,
during fdarray__filter(), a simple 'idx' is not enough. Add a pointer cookie
allows directly associate a 'st
This patch set enables daemonized perf recording by utilizing
overwritable backward ring buffer. With this feature one can
put perf background, and dump ring buffer records by a SIGUSR2
when he/she find something unusual. For example, following
command record system calls, schedule events and sampl
In perf_evlist__mmap_per_evsel(), select backward_mmap for backward events.
Utilize new perf_mmap APIs.
Remove useless functions.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: He Kuang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Zefan Li
Cc: Nilay Vaish
Cc: pi3or...
In perf_evlist__mmap_per_cpu() and perf_evlist__mmap_per_thread(), when
mmap failure, successfully created maps should be cleared.
Current code uses two loops __perf_evlist__munmap() for each function.
This patch extracts common code to perf_evlist__munmap_nofree() and
use previous introduced dec
Insetad of saving a index into fdarray entries private field, save the
corresponding 'struct perf_mmap' pointer, and release them directly
using perf_mmap__put().
Following commits introduce multiple mmap arrays to evlist. Without this
patch, perf_evlist__munmap_filtered() is unable to retrive cor
When working with overwritable ring buffer there's a inconvenience
problem: if perf dumps data after a long period after it starts, non-sample
events may lost, which makes following 'perf report' unable to identify
proc name and mmap layout. For example:
# perf record -m 4 -e raw_syscalls:* -g --
We are going to use evlist->backward_mmap as a container for backward
ring buffer. Since a evlist can hold normal and backward ring buffers
together, evlist->backward is useless and misleading. Drop this
indicator.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: He Kuang
Cc: Jiri Olsa
If write_backward attribute is set, records are written into kernel
ring buffer from end to beginning, but read from beginning to end.
To avoid 'XX out of order events recorded' warning message (timestamps
of records is in reverse order when using write_backward), suppress the
warning message if wr
Add backward_mmap to evlist. Alloc this array in perf_evlist__mmap_ex()
and free it together with normal mmap.
Signed-off-by: Wang Nan
Cc: Arnaldo Carvalho de Melo
Cc: He Kuang
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Cc: Zefan Li
Cc: Nilay Vaish
Cc: pi3or...@163.com
---
tools/
overwrite_evt_state is introduced to reflect the state of overwritable
ring buffers. It is a state machine with following states:
.(forbid)_.
| V
RUNNING --(1)--> DATA_PENDING --(2)--> EMPTY
^ ^ | ^
Currently, evlist mmap related helpers and APIs accept evlist and idx,
and dereference 'struct perf_mmap' by evlist->mmap[idx]. This is
unnecessary, and force a evlist contain only one mmap array.
Following commits are going to introduce multiple mmap array to evlist.
This patch refators those API
201 - 300 of 981 matches
Mail list logo
