Hi David,
On Thu, Nov 30, 2017 at 12:21 AM, David Daney wrote:
> On 11/29/2017 12:55 PM, Mathieu Malaterre wrote:
>>
>> Improve the binding example by removing all the leading 0x to fix the
>> following dtc warnings:
>>
>> Warning (unit_address_format): Node /XXX unit name should not have leading
On Wed 29-11-17 11:52:53, Mike Kravetz wrote:
> On 11/29/2017 01:22 AM, Michal Hocko wrote:
> > What about this on top. I haven't tested this yet though.
>
> Yes, this would work.
>
> However, I think a simple modification to your previous free_huge_page
> changes would make this unnecessary. I
Please add the patch version next time.
The patch make trackstick work on L570.
Tested-by: Aaron Ma
On 11/29/2017 04:33 PM, Masaki Ota wrote:
> From: Masaki Ota
> - The issue is that Thinkpad L570 TrackStick does not work. Because the main
> interface of Thinkpad L570 device is SMBus, so ALPS
2017-11-30 14:01 GMT+08:00 Wanpeng Li :
> From: Wanpeng Li
>
> Remote flushing api's does a busy wait which is fine in bare-metal
> scenario. But with-in the guest, the vcpus might have been pre-empted
> or blocked. In this scenario, the initator vcpu would end up
> busy-waiting for a long amount
On Thu, Nov 30, 2017 at 6:48 AM, Greentime Hu wrote:
> 2017-11-30 4:27 GMT+08:00 Arnd Bergmann :
>> On Wed, Nov 29, 2017 at 3:10 PM, Greentime Hu wrote:
>>> 2017-11-29 19:57 GMT+08:00 Arnd Bergmann :
On Wed, Nov 29, 2017 at 12:39 PM, Greentime Hu wrote:
> I think I can use this name "CPU_V3
On Thu, Nov 30, 2017 at 8:30 AM, Marek Szyprowski
wrote:
> Hi Krzysztof,
>
> On 2017-11-29 18:55, Krzysztof Kozlowski wrote:
>>
>> On Mon, Nov 27, 2017 at 7:12 PM, Krzysztof Kozlowski
>> wrote:
>>>
>>> On Fri, Nov 03, 2017 at 05:54:45PM +0100, Sylwester Nawrocki wrote:
The new sound car
> Thanks, applying all four for 4.16.--b.
Thank you very much!
Best Regards,
Elena.
>
> On Wed, Nov 29, 2017 at 01:15:42PM +0200, Elena Reshetova wrote:
> > This series, for lockd component, replaces atomic_t reference
> > counters with the new refcount_t type and API (see
> > include/linux/re
On Wed, Nov 29, 2017 at 04:41:45PM +0100, Daniel Vetter wrote:
> cross-release ftl
>
> From Chris:
>
> "Fwiw, this isn't cross-release but us reloading the module many times,
> creating a whole host of new lockclasses. Even more fun is when the
> module gets a slightly different address and the n
According to the TPM Library Specification, a TPM device must do a command
header validation before processing and return a TPM_RC_COMMAND_CODE code
if the command is not implemented.
So user-space will expect to handle that response as an error. But if the
in-kernel resource manager is used (/dev
On Wed, Nov 29, 2017 at 05:48:51PM +, Borislav Petkov wrote:
> On Wed, Nov 29, 2017 at 08:08:31PM +0300, Kirill A. Shutemov wrote:
> > We're really early in the boot -- startup_64 in decompression code -- and
> > I don't know a way print a message there. Is there a way?
> >
> > no_longmode han
Hi Krzysztof,
On 2017-11-29 18:55, Krzysztof Kozlowski wrote:
On Mon, Nov 27, 2017 at 7:12 PM, Krzysztof Kozlowski wrote:
On Fri, Nov 03, 2017 at 05:54:45PM +0100, Sylwester Nawrocki wrote:
The new sound card DT binding is used for Odroid XU3 in order
to properly support the HDMI audio path.
On Thu, Aug 3, 2017 at 5:32 AM, Lorenzo Pieralisi
wrote:
> This patch series is v3 of a previous posting:
>
> v2->v3:
> - Fixed DMA masks computation
> - Fixed size computation overflow in acpi_dma_get_range()
>
> v1->v2:
> - Reworked acpi_dma_get_range() flow and logs
>
Hi Maciej,
On Mon, Nov 27, 2017 at 11:34:44PM +0100, Maciej S. Szmigiero wrote:
> There is no problem in using different bit widths in playback and capture
> in AC'97 mode so allow this, too.
> @@ -1557,11 +1558,12 @@ static int fsl_ssi_probe(struct platform_device *pdev)
>
> /* Are the R
On Wed, Nov 29, 2017 at 09:38:52AM -0800, Florian Fainelli wrote:
>
> Hu, okay, I actually had a v3 prepared that I was going to post
> addressing some of the comments. Should I send an incremental set of
> changes now?
Please send it as an incremental set.
Thanks,
--
Email: Herbert Xu
Home Pag
On Wed, Nov 29, 2017 at 11:51:09AM -0800, Eric Biggers wrote:
>
> Herbert, if it's not too late can you fix the subject? It got split into two
> lines:
Sorry, it's already pushed out with other patches sitting on top
of it.
Cheers,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~he
On 2017/11/30 10:42, Yunlong Song wrote:
> SSR can make hot/warm/cold nodes written together, so why should we account
> them different?
Current segment which is using ssr allocation has only one valid type, so we
can not write data/node with different type into current segment which already
has f
Hi,
On Tuesday 28 November 2017 09:20 PM, Lorenzo Pieralisi wrote:
> On Thu, Nov 23, 2017 at 04:01:45PM +0100, Cyrille Pitchen wrote:
>> Hi all,
>>
>> this series of patches adds support to the Cadence PCIe controller.
>> It was tested on a ARM64 platform emulated by a Palladium running both
>> li
Hi David, Dan,
On Thu, Nov 30, 2017 at 12:50 AM, David Daney wrote:
> On 11/29/2017 08:07 AM, Souptick Joarder wrote:
>>
>> On Wed, Nov 29, 2017 at 4:00 PM, Souptick Joarder
>> wrote:
>>>
>>> On Wed, Nov 29, 2017 at 6:25 AM, David Daney
>>> wrote:
From: Carlos Munoz
The Ca
Hello Lukasz,
On Wed, 29 Nov 2017 23:07:04 +0100
Lukasz Majewski wrote:
> > > +/*
> > > + * BK3 support code
> > > +
> > > */
> > > +static struct mtd_p
On 2017/11/28 20:17, LiFan wrote:
> Avoid checking is_inode repeatedly, and make the logic
> a little bit clearer.
>
> Signed-off-by: Fan li
Reviewed-by: Chao Yu
Thanks,
On Wed 29-11-17 16:58:17, Matthew Wilcox wrote:
> On Wed, Nov 29, 2017 at 09:55:17PM +0800, Wei Wang wrote:
> > The was removed from radix-tree.h by the following commit:
> > f5bba9d11a256ad2a1c2f8e7fc6aabe6416b7890.
> >
> > Since that commit, tools/testing/radix-tree/ couldn't pass compilation
>
Hi Hyunchul,
On 2017/11/28 8:23, Hyunchul Lee wrote:
> From: Hyunchul Lee
>
> This implements which hint is passed down to block layer
> for datas from the specific segment type.
>
> segment type hints
> -
> COLD_NODE & COLD_DATA
On Tue, 28 Nov 2017, Greg KH wrote:
> On Mon, Nov 27, 2017 at 07:05:22PM -0500, Mikulas Patocka wrote:
> >
> >
> > On Sat, 25 Nov 2017, Greg KH wrote:
> >
> > > On Mon, Nov 13, 2017 at 02:00:45PM -0500, Mikulas Patocka wrote:
> > > > A small patch for schedule(), so that the code goes straght
Good Day,
I'm Wong Shiu a staff of Wing Hang Bank
here in Hong Kong. Can i TRUST you in transferring-
$13,991,674 USD? If yes do get back to me with my private email:
wong.shiu...@accountant.com
Best Regards
On 11/23/2017 05:52 AM, John Stultz wrote:
On Tue, Nov 21, 2017 at 12:17 AM, Hans Verkuil wrote:
If the device tree for a board did not specify a cec clock, then
adv7511_cec_init would return an error, which would cause adv7511_probe()
to fail and thus there is no HDMI output.
There is no ne
On 29-11-17, 16:50, Stephen Boyd wrote:
> Sorry it still makes zero sense to me. It seems that we're trying
> to make the OPP table parsing generic just for the sake of code
> brevity.
Not just the code but bindings as well to make sure we don't add a new
property (similar to earlier ones) for eve
On Wed 29-11-17 14:25:36, Kees Cook wrote:
> On Wed, Nov 29, 2017 at 6:42 AM, Michal Hocko wrote:
> > The first patch introduced MAP_FIXED_SAFE which enforces the given
> > address but unlike MAP_FIXED it fails with ENOMEM if the given range
> > conflicts with an existing one. The flag is introduc
On Wed 29-11-17 13:41:59, Andrew Morton wrote:
> On Wed, 29 Nov 2017 17:04:46 +0100 Michal Hocko wrote:
>
> > On Mon 27-11-17 12:33:41, Michal Hocko wrote:
> > > On Mon 27-11-17 19:09:24, JianKang Chen wrote:
> > > > From: Jiankang Chen
> > > >
> > > > __get_free_pages will return an virtual ad
> And once you disable it by default, and it becomes purely opt-in, that
> means that nothing will change for most cases. Some embedded people
> that do their own thing (ie Android) might change, but normal
> distributions probably won't.
>
> Yes, Android may be 99% of the users, and yes, the embe
On Wed, Nov 29, 2017 at 05:55:21PM -0800, Olof Johansson wrote:
> Fixes:
>
> drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer not
> defined for this architecture. [-Wcpp]
>
> Signed-off-by: Olof Johansson
> Cc: Dmitry Torokhov
Applied, thank you.
> ---
> drivers/input/
On 11/15/2017 03:29 PM, Lothar Waßmann wrote:
Hi,
On Tue, 14 Nov 2017 11:16:47 -0800 Eric Anholt wrote:
The panel_bridge bridge attaches to the panel's OF node, not the
lvds-encoder's node. Put in a little no-op bridge of our own so that
our consumers can still find a bridge where they expec
Hi,
On (11/30/17 10:26), Fengguang Wu wrote:
> FYI this happens in mainline kernel v4.15-rc1 .
> It shows up after v4.14 . Bisect is on the way.
hm, printk saw no changes between 4.14 and 4.15
> It occurs in 4 out of 4 boots.
>
> [0.00]RCU callback double-/use-after-free debug
On 11/29/2017, 07:19 PM, SF Markus Elfring wrote:
>>> It's pretty unlikely, but it is an actual defect.
>>
>> No it is not, those variables will never be set to NULL,
>> so this can never be triggered. Walk up the call chain.
>
> If the involved software developers are convinced about the validit
On 2017/11/28 8:23, Hyunchul Lee wrote:
> From: Hyunchul Lee
>
> This implements which hint is passed down to block layer
> for datas from the specific segment type.
>
> segment type hints
> -
> COLD_NODE & COLD_DATAWRITE_LIFE_
Hi, Ville
At 11/30/2017 05:25 AM, Ville Syrjälä wrote:
On Wed, Nov 29, 2017 at 09:15:19AM +0800, Dou Liyang wrote:
Hi Ville,
At 11/28/2017 10:53 PM, Ville Syrjala wrote:
From: Ville Syrjälä
This reverts commit b371ae0d4a194b178817b0edfb6a7395c7aec37a.
Causes my P3 UP machine to hang at boo
2017-11-30 0:21 GMT+08:00 Radim Krčmář :
> 2017-11-27 20:05-0800, Wanpeng Li:
>> From: Wanpeng Li
>>
>> Remote flushing api's does a busy wait which is fine in bare-metal
>> scenario. But with-in the guest, the vcpus might have been pre-empted
>> or blocked. In this scenario, the initator vcpu wou
Hi,
Some applications that uses System V IPC mechanisms rely on data
structures that are returned by ctl(..IPC_STAT..) system calls.
However, up to now information in these structures was not reliable,
due to following reasons:
1) Non-atomic data structures filling process, which, for obvious rea
On Wed, Nov 29, 2017 at 10:35:55AM +0100, Clement Courbet wrote:
> > > Note that on Arm (), the new c implementation still outperforms the
> > > old one that uses c+ the asm implementation of `find_next_bit` [3].
> > What is 'c+'? Is it typo?
>
> I meant "a mix of C and asm" ~(C + asm). Rephrased.
On 2017/11/28 8:23, Hyunchul Lee wrote:
> From: Hyunchul Lee
>
> When blocks are allocated for direct write, select the type of
> segment using the kiocb hint. But if an inode has FI_NO_ALLOC,
> use the inode hint.
>
> Signed-off-by: Hyunchul Lee
Reviewed-by: Chao Yu
Thanks,
As described in the title, this patch fixes id_ds inconsistency
when ctl_stat runs concurrently with some ds-changing function,
e.g. shmat, msgsnd or whatever.
For instance, if shmctl(IPC_STAT) is running concurrently with shmat,
following data structure can be returned:
{... shm_lpid = 0, shm_nat
This patch fixes that do_shmat increases shm_nattch value twice.
E.g. if memory segment was created just now and process attaches it,
shmctl(..IPC_STAT..) of concurrently running process can at some
point of time return data structure with 'shm_nattch' equal to 2.
Signed-off-by: Philippe Mikoyan
Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel,
it refactor Innolux P079ZCA panel driver, let it support
multi panel, and add support P097PFG panel in this driver.
Signed-off-by: Lin Huang
---
drivers/gpu/drm/panel/panel-innolux-p079zca.c | 178 --
1 file changed,
Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel,
it refactor Innolux P079ZCA panel driver, let it support
multi panel, and add support P097PFG panel in this driver.
Change-Id: If342e58a3de2861219b0b1313f402b6cb41ffa29
Signed-off-by: Lin Huang
---
drivers/gpu/drm/panel/panel-innolux-p079zca.
On Tue, Nov 28, 2017 at 10:07:36PM -0800, Moritz Fischer wrote:
> Hi Hao,
>
> first pass, I didn't get all the way through, yet.
Hi Moritz
Thanks a lot for your review and comments. :)
>
> On Mon, Nov 27, 2017 at 02:42:11PM +0800, Wu Hao wrote:
> > Device Feature List (DFL) defines a feature l
With latest kernel I get below bug while testing kdump:
[0.00] BUG: unable to handle kernel paging request at ea00034b1040
[0.00] IP: zero_resv_unavail+0xbd/0x126
[0.00] PGD 37b98067 P4D 37b98067 PUD 37b97067 PMD 0
[0.00] Oops: 0002 [#1] SMP
[0.00] Modu
Hi Stephen
On 11/30/17 03:35, Stephen Boyd wrote:
> On 11/28, Yixun Lan wrote:
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> index b932a784b02a..36a2e98338a8 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
>> +++ b/arch/ar
From: Wanpeng Li
This patch reuses the preempted field in kvm_steal_time, and will export
the vcpu running/pre-empted information to the guest from host. This will
enable guest to intelligently send ipi to running vcpus and set flag for
pre-empted vcpus. This will prevent waiting for vcpus that a
From: Wanpeng Li
Remote flushing api's does a busy wait which is fine in bare-metal
scenario. But with-in the guest, the vcpus might have been pre-empted
or blocked. In this scenario, the initator vcpu would end up
busy-waiting for a long amount of time.
This patch set implements para-virt flush
From: Wanpeng Li
Introduce a new bool invalidate_gpa argument to kvm_x86_ops->tlb_flush,
it will be used by later patches to just flush guest tlb.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Peter Zijlstra
Signed-off-by: Wanpeng Li
---
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/svm.c
From: Wanpeng Li
PV-Flush guest would indicate to flush on enter, flush the TLB before
entering the guest.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Peter Zijlstra
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/cpuid.c | 3 ++-
arch/x86/kvm/x86.c | 21 ++---
2 files changed, 16
Remote flushing api's does a busy wait which is fine in bare-metal
scenario. But with-in the guest, the vcpus might have been pre-empted
or blocked. In this scenario, the initator vcpu would end up
busy-waiting for a long amount of time.
This patch set implements para-virt flush tlbs making sure t
Hi Stephen
On 11/30/17 03:34, Stephen Boyd wrote:
> On 11/28, Yixun Lan wrote:
>> diff --git a/drivers/clk/meson/axg.c b/drivers/clk/meson/axg.c
>> new file mode 100644
>> index ..51c5b4062715
>> --- /dev/null
>> +++ b/drivers/clk/meson/axg.c
>> @@ -0,0 +1,948 @@
>> +/*
>> + * AmLogic
On 2017年11月29日 20:17, Michal Hocko wrote:
> On Tue 28-11-17 14:00:23, Kemi Wang wrote:
>> The existed implementation of NUMA counters is per logical CPU along with
>> zone->vm_numa_stat[] separated by zone, plus a global numa counter array
>> vm_numa_stat[]. However, unlike the other vmstat count
On Wed, Nov 29, 2017 at 09:53:48PM -0500, Joshua Abraham wrote:
> Signed-off-by: Joshua Abraham
>
> This patch removes the unused macro XGIPART3.
>
The Signed-off-by line goes after the changelog.
> ---
> drivers/staging/xgifb/XGI_main.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
2017-11-30 4:27 GMT+08:00 Arnd Bergmann :
> On Wed, Nov 29, 2017 at 3:10 PM, Greentime Hu wrote:
>> 2017-11-29 19:57 GMT+08:00 Arnd Bergmann :
>>> On Wed, Nov 29, 2017 at 12:39 PM, Greentime Hu wrote:
How about this?
choice
prompt "CPU type"
default C
> -Original Message-
> From: Haiyang Zhang
> Sent: Wednesday, November 29, 2017 16:55
> > -Original Message-
> > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> > Vitaly Kuznetsov writes:
> >
> > > While doing routing code review I noticed that commit 6df8d9aaf3af
> > > ("Dri
r/exit
operations
02a5c550b2 rcu: Abstract extended quiescent state determination
b915176102 Merge tag 'nfsd-4.15-1' of git://linux-nfs.org/~bfields/linux
d127129e85 Add linux-next specific fi
On Tuesday 28 November 2017 05:22 PM, Mark Brown wrote:
On Tue, Nov 28, 2017 at 10:13:44AM +0530, Vijendar Mukunda wrote:
- acp_init(audio_drv_data->acp_mmio, audio_drv_data->asic_type);
+ status = acp_init(audio_drv_data->acp_mmio, audio_drv_data->asic_type);
+ if (status)
'add_efi_memmap' is an early param, but do_add_efi_memmap() has no
chance to run because the code path is before parse_early_param().
I believe it worked when the param was introduced but probably later
some other changes caused the wrong order and nobody noticed it.
Move parse_early_param before
Ian Kent writes:
> On 30/11/17 08:01, Eric W. Biederman wrote:
>>
>> While reviewing some code I realized that in getting d_automount working
>> with s_user_ns I had left behind some unnecessary relics of the blind
>> path I started down. Here are two patches that remove those relics.
>>
>> Un
On Thu, Nov 30, 2017 at 09:38:01AM +0800, Fengguang Wu wrote:
> This is perhaps the most clean solution. Thank you for the patch! -fengguang
After thinking about it some more, I think we should just remove the
printk altogether. I suspect it was added with the thought that it
would help debug th
On Wed, Nov 29, 2017 at 08:41:36PM -0800, Joe Perches wrote:
> On Thu, 2017-11-30 at 15:18 +1100, Tobin C. Harding wrote:
> > On Wed, Nov 29, 2017 at 07:58:26PM -0800, Joe Perches wrote:
> > > On Thu, 2017-11-30 at 10:26 +1100, Tobin C. Harding wrote:
> > > > On Wed, Nov 29, 2017 at 03:20:58PM -080
On 29-11-17, 10:46, Rob Herring wrote:
> On Tue, Oct 31, 2017 at 7:47 AM, Viresh Kumar wrote:
> > +- power-domain-opp: This contains phandle to one of the OPP nodes of the
> > master
> > + power domain. This specifies the minimum required OPP of the master
> > domain for
> > + the functioning
From: "Gautham R. Shenoy"
Pstates are 8bit values but on POWER8 they are negative and on POWER9
they are positive. This patch adds helper routines to differentiate
the sign to read the correct pstate value.
Signed-off-by: Gautham R. Shenoy
Tested-by: Shilpasri G Bhat
---
drivers/cpufreq/power
On Thu, 2017-11-30 at 15:18 +1100, Tobin C. Harding wrote:
> On Wed, Nov 29, 2017 at 07:58:26PM -0800, Joe Perches wrote:
> > On Thu, 2017-11-30 at 10:26 +1100, Tobin C. Harding wrote:
> > > On Wed, Nov 29, 2017 at 03:20:58PM -0800, Andrew Morton wrote:
> > > > On Wed, 29 Nov 2017 13:05:04 +1100 "T
On 2017/11/29 22:14, Dou Liyang wrote:
> Hi Jiang,
>
> At 11/29/2017 09:44 PM, zhong jiang wrote:
>> On 2017/11/29 21:33, Michal Hocko wrote:
>>> On Wed 29-11-17 21:26:19, zhong jiang wrote:
On 2017/11/29 21:01, Michal Hocko wrote:
> On Wed 29-11-17 20:41:25, zhong jiang wrote:
>> On 2
On Wed, Nov 29, 2017 at 06:44:43PM -0800, Linus Torvalds wrote:
On Wed, Nov 29, 2017 at 6:38 PM, Nick Terrell wrote:
The stack trace looks like the bug fixed by
Qu Wenruo:
btrfs: Fix wild memory access in compression level parser [1]
That fix looks to be included in the pull request for
On Wed, Nov 29, 2017 at 10:43:33PM +0800, Jason Wang wrote:
>
>
> On 2017年11月29日 22:23, w...@redhat.com wrote:
> > From: Wei Xu
> >
> > Matthew found a roughly 40% tcp throughput regression with commit
> > c67df11f(vhost_net: try batch dequing from skb array) as discussed
> > in the following t
Occasionally the following error message can be seen in the logs of
Qualcomm devices using UFS:
EXT4-fs (sda9): Delayed block allocation failed for inode 685600 at logical
offset 1086 with max blocks 3 with error 121
EXT4-fs (sda9): This should not happen!! Data will be lost
This is caused by a
On Wed, Nov 29, 2017 at 07:58:26PM -0800, Joe Perches wrote:
> On Thu, 2017-11-30 at 10:26 +1100, Tobin C. Harding wrote:
> > On Wed, Nov 29, 2017 at 03:20:58PM -0800, Andrew Morton wrote:
> > > On Wed, 29 Nov 2017 13:05:04 +1100 "Tobin C. Harding"
> > > wrote:
> > >
> > > > printk specifier %p
On Thu, Nov 30, 2017 at 02:07:19AM +, Al Viro wrote:
> FWIW, looking through the callers of sock_alloc_file()... we might be
> better off if it did sock_release() on failure. Then the calling
> conventions become "sock_alloc_file() means not calling sock_release()
> directly - either it'll be
On Wed, 29 Nov 2017 19:44:33 -0800
Linus Torvalds wrote:
I keep older compilers around to test ftrace before -mfentry was
introduced.
I wonder if I should just add a config to force the use without
-mfentry even if the compiler supports it.
> fs/nfs/nfs4state.c | 3 +--
> include/linux/nfs4.
Currently we have a rblist__delete() which is used to delete a rblist.
While rblist__delete() will free the pointer of rblist at the end.
It's inconvenience for user to delete a rblist which is not allocated
by something like malloc(). For example, the rblist is defined in a
data structure.
This
Previously the rbtree was used to link generic metrics.
This patches adds new ctx/type/stat into rbtree keys because we
will use this rbtree to maintain shadow metrics to replace original
a couple of static arrays for supporting per-thread shadow stats.
Signed-off-by: Jin Yao
---
tools/perf/uti
Perf has a set of static variables to record the runtime shadow
metrics stats.
While if we want to record the runtime shadow stats for per-thread,
it will be the limitation. This patch creates a structure and the
next patches will use this structure to update the runtime shadow
stats for per-threa
It mainly initializes the rblist in struct runtime_stat.
For the original rblist 'runtime_saved_values', it's still there
for keeping the patch bisectable. The rblist 'runtime_saved_values'
will be removed in later patch at switching time.
Signed-off-by: Jin Yao
---
tools/perf/util/stat-shadow.
On Wed, Nov 29, 2017 at 11:38:26AM -0500, Serhii Popovych wrote:
> There is no need to pass it explicitly from the caller:
> struct kvm_resize_hpt already contains it.
>
> Additional benefit from this change is that BUG_ON()
> assertion now checks that mutex is held on kvm instance
> associated wi
On Wed, Nov 29, 2017 at 11:38:22AM -0500, Serhii Popovych wrote:
> It is possible to trigger use after free during HPT resize
> causing host kernel to crash. More details and analysis of
> the problem can be found in change with corresponding subject
> (KVM: PPC: Book3S HV: Fix use after free in ca
On Wed, Nov 29, 2017 at 11:38:25AM -0500, Serhii Popovych wrote:
> When serving multiple resize requests following could happen:
>
> CPU0CPU1
>
> kvm_vm_ioctl_resize_hpt_prepare(1);
> -> schedule_wor
On Wed, Nov 29, 2017 at 11:38:24AM -0500, Serhii Popovych wrote:
> There are several points of improvements:
>
> 1) Make kvmppc_free_hpt() check if allocation is made before attempt
> to release. This follows kfree(p) semantics where p == NULL.
>
> 2) Return initialized @info parameter f
On Wed, Nov 29, 2017 at 11:38:23AM -0500, Serhii Popovych wrote:
> Replace ->prepare_done flag functionality with special handling
> of -EBUSY in ->error as indicator that allocation work is running.
>
> Besides cosmetics this reduces size of struct kvm_resize_hpt by
> __alignof__(struct kvm_hpt_i
In previous patches, we have reconstructed the code and let
it not access the static variables directly.
This patch removes these static variables.
Signed-off-by: Jin Yao
---
tools/perf/util/stat-shadow.c | 68 ++-
tools/perf/util/stat.h| 1 +
2
After perf_evlist__create_maps() being executed, we can get all
threads from /proc. And via thread_map__nr(), we can also get
the number of threads.
With the number of threads, the patch allocates a buffer which
will record the shadow stats for these threads.
The buffer pointer is saved in stat_c
There are many threads reported if we enable '--per-thread'
globally.
1. Most of the threads are not counted or counting value 0.
This patch removes these threads.
2. We also resort the threads in display according to the
counting value. It's useful for user to see the hottest
threads easily.
Fo
Currently, if we execute 'perf stat --per-thread' without specifying
pid/tid, perf will return error.
root@skl:/tmp# perf stat --per-thread
The --per-thread option is only available when monitoring via -p -t options.
-p, --pidstat events on existing process id
-t, --tidstat
In current stat-shadow.c, the rbtree deleting is ignored.
The patch adds the implementation to node_delete method
of rblist.
Signed-off-by: Jin Yao
---
tools/perf/util/stat-shadow.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/stat-shadow.c b/
The functions perf_stat__update_shadow_stats() and
perf_stat__print_shadow_statss() are called to update
and print the shadow stats on a set of static variables.
But the static variables are the limitations to support
per-thread shadow stats.
This patch lets the perf_stat__update_shadow_stats() s
Perf already has a function thread_map__new_by_uid() which can
enumerate all threads from /proc by uid.
This patch creates a static function enumerate_threads() which
reuses the common code in thread_map__new_by_uid() to enumerate
threads from /proc.
The enumerate_threads() is shared by thread_ma
If the stats pointer in stat_config structure is not null, it will
update the per-thread stats or print the per-thread stats on this
buffer.
Signed-off-by: Jin Yao
---
tools/perf/builtin-stat.c | 9 +++--
tools/perf/util/stat.c| 11 ---
2 files changed, 15 insertions(+), 5 delet
v4:
---
Update according to Jiri's comments. The major modification is:
Move struct perf_stat_config::*stats|stats_num to
'perf stat: Allocate shadow stats buffer for threads'.
I also move the code of updating/printing per-thread stats
from 'perf util: Update and print per-thread shadow stats'
an
On Thu, 2017-11-30 at 10:26 +1100, Tobin C. Harding wrote:
> On Wed, Nov 29, 2017 at 03:20:58PM -0800, Andrew Morton wrote:
> > On Wed, 29 Nov 2017 13:05:04 +1100 "Tobin C. Harding" wrote:
> >
> > > printk specifier %p now hashes all addresses before printing. Sometimes
> > > we need to see the a
General support for state persistence is added to gpiolib with the
introduction of a new pinconf parameter to propagate the request to
hardware. The existing persistence support for sleep is adapted to
include hardware support if the GPIO driver provides it. Persistence
continues to be enabled by d
Hello,
This series provides an API to configure general GPIO state persistence in
gpiolib. Previously, only sleep persistence was considered, but controllers
like one found in Aspeed BMCs also support persistence of state across
controller resets. There is some prior discussion on v1[1] and the in
Use the new pinconf parameter for state persistence to expose the
associated capability of the Aspeed GPIO controller.
Signed-off-by: Andrew Jeffery
Reviewed-by: Joel Stanley
---
drivers/gpio/gpio-aspeed.c | 39 +--
1 file changed, 37 insertions(+), 2 deletio
Hi all,
Changes since 20171129:
Dropped tree: vfs (badly conflicting commit)
The vfs tree still had bad conflicts against Linus' tree so I dropped
it again for today.
The etnaviv tree still had its build failure, so I used the version from
next-20171127.
The sound-asoc tree lost its
>> Hi Mel,
>>
>> The forth approach is the best as it is seamless for admins and
>> engineers, it will also work on any system configuration with any
>> parameters without any special involvement.
>
> Apart from what-mel-said, I'd be concerned that this failsafe would
> almost never get tested. We
On Wed, 29 Nov 2017 19:44:33 -0800 Linus Torvalds
wrote:
> On Wed, Nov 29, 2017 at 7:39 PM, Andrew Morton
> wrote:
> >
> > Yeah, I'm the world expert at working around this gcc bug but the nfs4
> > one had me stumped when I looked at it, so I shelved it for revisiting
> > later.
>
> Does the a
From: Changbin Du
The default NR_CPUS can be very large, but actual possible nr_cpu_ids
usually is very small. For my x86 distribution, the NR_CPUS is 8192 and
nr_cpu_ids is 4. About 2 pages are wasted.
Most machines don't have so many CPUs, so define a array with NR_CPUS
just wastes memory. So
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (sparc
defconfig) failed like this:
mm/list_lru.c: In function 'list_lru_del':
mm/list_lru.c:141:2: error: implicit declaration of function 'prefetchw'
[-Werror=implicit-function-declaration]
prefetchw(item->prev);
^
C
On Wed, Nov 29, 2017 at 7:39 PM, Andrew Morton
wrote:
>
> Yeah, I'm the world expert at working around this gcc bug but the nfs4
> one had me stumped when I looked at it, so I shelved it for revisiting
> later.
Does the attached patch fix it? I don't have old compilers.
Linus
fs/nfs/
1 - 100 of 1346 matches
Mail list logo
