On Wed, Oct 05, 2016 at 02:23:22AM +0530, Harman Kalra wrote:
> 2 errors "open brace { should be on the previous line" are fixed.
> Warning "Prefer "pr_debug over printk(KERN_DEBUG... " fixed
> Few line more tahn 80 character warnings fixed
That's three different things, please make three differen
On Wed, Oct 05, 2016 at 01:40:05AM +0100, Alasdair G Kergon wrote:
> On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
> > devicemapper is using uevents for:
> > a. dm-verity detected corruption
> > b. dm-multipath: path failed or reinstated
> > c. dm device renamed
> > d. there's also s
On Tue, Oct 04, 2016 at 11:06:15AM +0200, Jan Kara wrote:
> On Tue 04-10-16 10:53:40, Pierre Morel wrote:
> > When triggering thaw-filesystems via magic sysrq, the system enters a
> > loop in do_thaw_one(), as thaw_bdev() still returns success if
> > bd_fsfreeze_count == 0. To fix this, let thaw_bd
FYI, the patches look fine to me:
Acked-by: Christoph Hellwig
but we're past the merge window for 4.9 now unfortunately.
On Tue, Oct 04, 2016 at 07:55:12PM -0300, Mauricio Faria de Oliveira wrote:
> Hi Benjamin, Kent, and others,
>
> Would you please comment / answer about this possible problem?
> Any feedback is appreciated.
>
> Since commit e1bdd5f27a5b ("aio: percpu reqs_available") the maximum
> number of aio n
On 10/05/16 09:21, Mugunthan V N wrote:
> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote:
>> On 10/03/16 16:03, Mugunthan V N wrote:
>>> +static int tiadc_request_dma(struct platform_device *pdev,
>>> +struct tiadc_device *adc_dev)
>>> +{
>>> + struct tiadc_dma
On 10/05/2016 02:40 AM, Alasdair G Kergon wrote:
> On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
>> devicemapper is using uevents for:
>> a. dm-verity detected corruption
>> b. dm-multipath: path failed or reinstated
>> c. dm device renamed
>> d. there's also some use in md and bcach
On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote:
> On 10/03/16 16:03, Mugunthan V N wrote:
>> +static int tiadc_request_dma(struct platform_device *pdev,
>> + struct tiadc_device *adc_dev)
>> +{
>> +struct tiadc_dma*dma = &adc_dev->dma;
>> +dma_cap_
On Tue, Oct 04, 2016 at 06:02:14PM -0700, Davidlohr Bueso wrote:
> On Mon, 03 Oct 2016, Peter Zijlstra wrote:
> >Do people have more/better futex-pi test cases?
>
> pi_stress.
Where does one find that? Link?
On Tue, Oct 04, 2016 at 08:57:55PM -0700, Davidlohr Bueso wrote:
> On Mon, 03 Oct 2016, Peter Zijlstra wrote:
>
> >Since the futex_q can dissapear the instruction after assigning NULL,
> >this really should be a RELEASE barrier. That stops loads from hitting
> >dead memory too.
> >
> >Signed-off-b
On 05/10/16 05:07, Adam Ford wrote:
> Make "HDMI for OMAP4" and "HDMI for OMAP5" depend on ARCH_OMAP4
> and SOC_OMAP5/DRA7XX respectively.
>
> Signed-off-by: Adam Ford
>
> Changes in v2: Add dependancy for DRA7XX or OMAP5
You don't say it, but I presume this is just to make those kconfig
option
On 4 October 2016 at 11:46, Mylène Josserand
wrote:
> Add the audio card for sun8i SoC. This card links the codec driver
> (digital part) with the DAI driver. The analog codec driver is
> added as an aux_device.
>
> Signed-off-by: Mylène Josserand
> ---
> sound/soc/sunxi/Kconfig | 14 +++
>
s/ALIVEC/ALTIVEC/
Signed-off-by: Valentin Rothberg
---
arch/powerpc/kernel/process.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index 9e7c10fe205f..ce6dc61b15b2 100644
--- a/arch/powerpc/kernel/process.c
+++ b
On Tue 04-10-16 09:39:48, Ross Zwisler wrote:
> > The gfp_mask that propagates from __do_fault() or do_page_mkwrite() is fine
> > because at that point it is correct. But once we grab filesystem locks
> > which are not reclaim safe, we should update vmf->gfp_mask we pass further
> > down into DAX c
On Tue 04-10-16 15:56:39, Al Viro wrote:
> On Tue, Oct 04, 2016 at 11:00:41AM +0200, Jan Kara wrote:
> > Hi!
> >
> > On Mon 03-10-16 16:30:55, Tony Lindgren wrote:
> > > I'm seeing a repeatable oops with Linux next while running
> > > update-initramfs, see below. I tried reverting commit 59aa5a3ae
On Tue, Oct 04, 2016 at 08:29:00PM -0700, Linus Torvalds wrote:
> So what I think we should think about is:
>
> - extending the checkpatch warning to VM_BUG_ON too, to discourage new users.
>
> - look at making BUG_ON() simply be less lethal. Remove the
> unrechable(), reorganize how the string
The build of mips ath79_defconfig was failing with the error:
drivers/watchdog/ath79_wdt.c:164:5:
error: implicit declaration of function 'get_user'
drivers/watchdog/ath79_wdt.c:196:3:
error: implicit declaration of function 'copy_to_user'
drivers/watchdog/ath79_wdt.c:201:3:
On Tue, Oct 04, 2016 at 08:43:03PM -0300, Gaston Gonzalez wrote:
> Hi,
>
> After hibernation I get the following error when I tried to connect to monitor
> through hdmi:
>
> $ xrandr --output LVDS1 --off --output HDMI1 --auto
> xrandr: Configure crtc 1 failed
>
> This does not happen in kernel
On 22-09-16, 19:54, Andreas Herrmann wrote:
> On Mon, Sep 19, 2016 at 10:39:18PM +0300, Stratos Karafotis wrote:
> > Just an idea. I would split the frequency range (max_freq - min_freq)
> > into ~10 steps. But I'm not familiar with the affected systems and
> > of course I can't prove this is an id
Sorry for being late Andreas :(
On 14-09-16, 16:56, Andreas Herrmann wrote:
First of all, thanks for your hardwork in getting these numbers out.
Really appreciate it.
> Below is some trace data. I hope it is of some help.
>
> (A) - sampling 10s period when system is idle
> (B) - sampling 10s pe
Hi all,
There will be no linux-next release on Friday.
Please do *not* add any v4.10 material to your linux-next included trees
until v4.9-rc1 has been released i.e. the merge window closes.
Changes since 20161004:
Non-merge commits (relative to Linus' tree): 11868
8531 files changed, 4
Hi Guenter,
On 10/05/2016 11:10 AM, Guenter Roeck wrote:
> On Tue, Oct 04, 2016 at 09:09:10PM +, Chris Packham wrote:
>>
>>>
>>> Of course, all that doesn't solve the real problem in this driver, which is
>>> that it ignores error codes from the smbus functions, but that is a
>>> different
>>
From: Kalle Valo
Date: Wed, 05 Oct 2016 07:50:39 +0300
> net-next still fails to compile for me. I verified that these two
> patches fix it but I don't see them in net-next yet.
Pablo please get those fixes to me as soon as possible.
Aaron Conole writes:
> David Miller writes:
>
>> From: Kalle Valo
>> Date: Thu, 29 Sep 2016 19:57:28 +0300
>>
> ...
>>> Or actually I had one problem. While doing a test merge I noticed that
>>> net-next fails to compile for me, but I don't think this is anything
>>> wireless related:
>>>
>>>
Hi Anand,
On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote:
> Hi Vivek,
>
[snip]
>
> What I feel is that their need to be some reset of usb phy so that
> device are assigned to respective bus ports.
The phy resets are what we do in the phy-exynos5-usbdrd driver. In
addition to what we
have cu
Hi,
Thanks for youre review.
> -Original Message-
> From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees
> Cook
> Sent: Friday, September 09, 2016 6:23 AM
> To: 岩松信洋 / IWAMATSU，NOBUHIRO
> Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML; Hiraku Toyooka; Mark
> Salyzy
Hi,
> -Original Message-
> From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees
> Cook
> Sent: Friday, September 09, 2016 6:34 AM
> To: 岩松信洋 / IWAMATSU，NOBUHIRO
> Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML; Hiraku Toyooka; Mark
> Salyzyn; 阿口誠司 / AGUCHI，SEIJI
> Su
On Tue, Oct 04, 2016 at 08:00:18PM -0700, John Stultz wrote:
> On Tue, Oct 4, 2016 at 5:38 PM, Serge E. Hallyn wrote:
> > Quoting John Stultz (john.stu...@linaro.org):
> >> So this patch, as suggested by Tejun, simply adds a new process
> >> capability flag (CAP_CGROUP_MIGRATE_TASK), and uses it
Hi,
> -Original Message-
> From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees
> Cook
> Sent: Friday, September 09, 2016 6:56 AM
> To: 岩松信洋 / IWAMATSU，NOBUHIRO
> Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML; Hiraku Toyooka; Mark
> Salyzyn; 阿口誠司 / AGUCHI，SEIJI; Shu
Hi,
> -Original Message-
> From: keesc...@google.com [mailto:keesc...@google.com] On Behalf Of Kees
> Cook
> Sent: Friday, September 09, 2016 6:53 AM
> To: 岩松信洋 / IWAMATSU，NOBUHIRO
> Cc: Anton Vorontsov; Colin Cross; Tony Luck; LKML; Hiraku Toyooka; Mark
> Salyzyn; 阿口誠司 / AGUCHI，SEIJI
> Su
The Sharp 15" LQ150X1LG11 panel is an XGA TFT LCD panel.
Signed-off-by: Peter Rosin
---
.../bindings/display/panel/sharp,lq150x1lg11.txt | 36 ++
1 file changed, 36 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/sharp,lq150x1lg11.txt
dif
On 23-09-16, 19:02, Andreas Herrmann wrote:
> Introduce op for ondemand governor that is used to map load to
> frequency. It allows a cpufreq driver to provide a specific mapping
> function if the generic function is not optimal for the driver.
>
> Performance results (kernel compile with differen
On Mon, 03 Oct 2016, Peter Zijlstra wrote:
futex_top_waiter() returns the top-waiter on the pi_mutex. Assinging
this to a variable 'match' totally obscures the code.
Signed-off-by: Peter Zijlstra (Intel)
Reviewed-by: Davidlohr Bueso
On Mon, 03 Oct 2016, Peter Zijlstra wrote:
Since the futex_q can dissapear the instruction after assigning NULL,
this really should be a RELEASE barrier. That stops loads from hitting
dead memory too.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/futex.c |3 +--
1 file changed, 1 inserti
On 5 October 2016 at 08:24, Horng-Shyang Liao wrote:
> On Fri, 2016-09-30 at 17:47 +0800, Horng-Shyang Liao wrote:
>> On Fri, 2016-09-30 at 17:11 +0800, CK Hu wrote:
>
> After I trace mailbox driver, I realize that CMDQ driver cannot use
> tx_done.
>
> CMDQ clients will flush many tasks into CMDQ
For 32bit systems whose bootloader doesn't set the extended 36-bit
addressing register for flash devices above the 4GB boundary
we can set up in the driver.
This patch checks the number of address-cells in the dts file
for the fsl-ifc flash controller. If #address-cells is 2 then
it's a 36-bit ad
On Tuesday 04 October 2016 06:41 PM, Lokesh Vutla wrote:
>
> On Tuesday 04 October 2016 06:26 PM, Mugunthan V N wrote:
>> > The default impedance settings of the phy is not the optimal
>> > value, due to this the second ethernet is not working. Fix it
>> > with correct values which makes the secon
On Tuesday 04 October 2016 06:40 PM, Andrew Lunn wrote:
>> +if (of_property_read_bool(of_node, "ti,max-output-imepdance"))
>> +dp83867->io_impedance = DP83867_IO_MUX_CFG_IO_IMPEDANCE_MAX;
>> +else if (of_property_read_bool(of_node, "ti,min-output-imepdance"))
>
> Did you really
On Tue, Oct 4, 2016 at 7:43 PM, Paul Gortmaker
wrote:
>
> A couple years ago Ingo had an idea to kill BUG_ON abuse that I made
> a 1st pass at. Back then it seemed nobody cared. Maybe that has since
> changed?
>
> https://lkml.org/lkml/2014/4/30/359
So we actually have the checkpatch warning a
On 30-09-16, 14:55, Markus Mayer wrote:
> Add the binding document for the new brcmstb-avs-cpufreq driver.
>
> Signed-off-by: Markus Mayer
> ---
> .../bindings/cpufreq/brcm,stb-avs-cpu-freq.txt | 77
> ++
> MAINTAINERS| 7 ++
> 2
On 30-09-16, 14:56, Markus Mayer wrote:
> In order to aid debugging, we add a debugfs interface to the driver
> that allows direct interaction with the AVS co-processor.
>
> The debugfs interface provides a means for reading all and writing some
> of the mailbox registers directly from the shell p
On 30-09-16, 14:56, Markus Mayer wrote:
> This driver supports voltage and frequency scaling on Broadcom STB SoCs
> using AVS firmware with DFS and DVFS support.
>
> Actual frequency or voltage scaling is done exclusively by the AVS
> firmware. The driver merely provides a standard CPUfreq interfa
On Tue, Oct 4, 2016 at 5:38 PM, Serge E. Hallyn wrote:
> Quoting John Stultz (john.stu...@linaro.org):
>> So this patch, as suggested by Tejun, simply adds a new process
>> capability flag (CAP_CGROUP_MIGRATE_TASK), and uses it when checking
>
> So realistically, what all can this mean? Freezing
On Wed, Oct 5, 2016 at 12:24 AM, Maxime Ripard
wrote:
> Hi,
>
> On Tue, Oct 04, 2016 at 11:46:21AM +0200, Mylène Josserand wrote:
>> Add the documentation for dt-binding of the analog audiocodec
>> driver for SUN8I SoC.
>>
>> Signed-off-by: Mylène Josserand
>> ---
>> .../devicetree/bindings/soun
In commit 27727df240c7 ("Avoid taking lock in NMI path with
CONFIG_DEBUG_TIMEKEEPING"), I changed the logic to open-code
the timekeeping_get_ns() function, but I forgot to include
the unit conversion from cycles to nanoseconds, breaking the
function's output, which impacts users like perf.
This wo
On Fri, 2016-09-30 at 17:47 +0800, Horng-Shyang Liao wrote:
> On Fri, 2016-09-30 at 17:11 +0800, CK Hu wrote:
> > Hi, HS:
> >
> > One comment inline
> >
> > On Fri, 2016-09-30 at 16:56 +0800, Horng-Shyang Liao wrote:
> > > Hi CK,
> > >
> > > Please see my inline reply.
> > >
> > > On Fri, 2016-
On Tue, Oct 4, 2016 at 12:00 AM, Linus Torvalds
wrote:
[...]
> I should have reacted to the damn added BUG_ON() lines. I suspect I
> will have to finally just remove the idiotic BUG_ON() concept once and
> for all, because there is NO F*CKING EXCUSE to knowingly kill the
> kernel.
A couple year
On Fri, 2016-23-09 at 20:35:00 UTC, "Naveen N. Rao" wrote:
> While at it, ensure that the location of the local save area is
> consistent whether or not we setup our own stackframe. This property is
> utilised in the next patch that adds support for tail calls.
>
> Signed-off-by: Naveen N. Rao
S
On Fri, 2016-29-07 at 03:55:34 UTC, Andrew Donnellan wrote:
> Rewrite the cxl_guest_init_afu() loop in cxl_of_probe() to use
> for_each_child_of_node() rather than a hand-coded for loop.
>
> Remove the useless of_node_put(afu_np) call after the loop, where it's
> guaranteed that afu_np == NULL.
>
Emilio López writes:
> Hi,
>
> El 27/09/16 a las 01:23, Michael Ellerman escribió:
>> Emilio López writes:
>>> El 22/09/16 a las 06:43, Michael Ellerman escribió:
Emilio López writes:
Please don't include the *kernel* headers, they're really not meant to
be used in userspace
Hi Anton,
I was reading the powerpc syscall entry code and git points me at your commit
05b05f28 (powerpc: Relocatable system call no longer uses the LR) for one
part that confused me, so I hope you don't mind a quick question. In particular,
that commit removed the use of r10 to restore lr, but d
On Tue, Oct 4, 2016 at 5:34 PM, wrote:
> From: Rik van Riel
>
> Now that fpregs_activate and fpregs_deactivate do nothing except
> call the double underscored versions of themselves, we can get
> rid of the double underscore version.
Reviewed-by: Andy Lutomirski
On Tue, Oct 4, 2016 at 5:34 PM, wrote:
> From: Rik van Riel
>
> Name the functions after the state they track, rather than the function
> they currently enable. This should make it more obvious when we use the
> fpu_register_state_valid function for something else in the future.
I like this.
R
Make "HDMI for OMAP4" and "HDMI for OMAP5" depend on ARCH_OMAP4
and SOC_OMAP5/DRA7XX respectively.
Signed-off-by: Adam Ford
Changes in v2: Add dependancy for DRA7XX or OMAP5
diff --git a/drivers/gpu/drm/omapdrm/dss/Kconfig
b/drivers/gpu/drm/omapdrm/dss/Kconfig
index d1fa730..befdd7a 100644
---
On Tue, Oct 4, 2016 at 5:34 PM, wrote:
> From: Rik van Riel
>
> With the lazy FPU code gone, we no longer use the counter field
> in struct fpu for anything. Get rid it.
Reviewed-by: Andy Lutomirski
Hi Sergey,
On Tue, Oct 04, 2016 at 01:43:14PM +0900, Sergey Senozhatsky wrote:
< snip >
> TEST
>
>
> new tests results; same tests, same conditions, same .config.
> 4-way test:
> - BASE zram, fio direct=1
> - BASE zram, fio fsync_on_close=1
> - NEW zram, fio direct=1
> - NEW zram, fio fsyn
On Tue, Oct 4, 2016 at 6:48 PM, Josh Triplett wrote:
>
>I definitely don't think it
> should be a system-wide "mount event"; it should be a per-device "go
> direct-load your firmware" poke from userspace.
I don't disagree with that kind of interface. We already have things
like "rescan" for P
On Tue, Oct 04, 2016 at 05:12:58PM -0700, Linus Torvalds wrote:
> On Tue, Oct 4, 2016 at 5:00 PM, Luis R. Rodriguez wrote:
> > I am not sure how/why a firmware loading daemon would be a better
> > idea now. What Marc describes that Josh proposed with signals for
> > userspcae seems more aligned wi
On (10/04/16 14:22), Petr Mladek wrote:
[..]
> if (retry && console_trylock())
> goto again;
>
> with a safe variant, something like
>
> if (retry) {
> local_irq_save(flags);
> alt_printk_enter();
> lock_failed = console_trylock(
On 04-10-16, 17:26, Viresh Kumar wrote:
> diff --git a/include/linux/pm_opp.h b/include/linux/pm_opp.h
> +int dev_pm_opp_register_set_rate_helper(struct device *dev,
> + int (*set_rate)(struct device *dev, struct dev_pm_set_rate_data *data))
> +{
> + return -ENOTSUPP;
> +}
+ this to fix up
On (10/04/16 16:52), Petr Mladek wrote:
> >
> > Or is there any other catch that I do not see at the moment?
>
> And there is :-( The above logic looked at the problem only from
> one side. It was about errors starting from the printk()
> code itself, for example:
yes, like I said - printk recur
On Tue, Oct 4, 2016 at 2:32 AM, Johannes Weiner wrote:
>
> In the workingset code, if we detect radix tree nodes in a state in
> which they shouldn't be on the shadow node LRU, we could simply warn,
> abort the reclaim process and leave them off the LRU. Something like
> the below patch.
I don't
On Mon, 03 Oct 2016, Peter Zijlstra wrote:
These are unused and clutter up the code.
Signed-off-by: Peter Zijlstra (Intel)
Reviewed-by: Davidlohr Bueso
On Mon, 03 Oct 2016, Peter Zijlstra wrote:
Hi,
During my last PI failing patch set it became obvious there's a number of
related fail in FUTEX_UNLOCK_PI that needed sorting before we can move on
with that stuff.
These here patches are the result of staring at that code for a wee bit.
Please
There is no need to explicitly initiate a register transfer and
turn off the DCU after initializing the plane registers. In fact,
this is harmful and leads to unnecessary flickers if the DCU has
been left on by the bootloader.
Signed-off-by: Stefan Agner
---
If you could give this and 3/3 a try o
Hi Justin,
2016-10-05 6:02 GMT+08:00 Justin Piszcz :
> Hello,
>
> kernel 4.8 with ulogd-2.0.5- IPs are no longer logged:
>
> Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT=
> MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00
> TTL=0 ID=0 PROTO=0 MARK=0
> Oct 4 17:51:31 atom INPUT
Do not use encoder disable/enable callbacks to control bypass
mode as this seems to mess with the signals not liked by
displays. This also makes more sense since the encoder is
already defined to be parallel RGB/LVDS at creation time.
Signed-off-by: Stefan Agner
---
I tested that on Vybrid. Meng,
The pixel clock should not be on if the CRTC is not in use, hence
move clock enable/disable calls into CRTC callbacks.
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 7 +++
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 16 +---
2 files changed, 8 ins
Hey David,
The use of this function is going from the private member to the
public netdev struct. The usage is desired from the following coding
pattern.
You're implementing a netdevice. You've got ndo_init, ndo_uninit,
ndo_open, ndo_stop, ndo_start_xmit, and maybe even ndo_do_ioctl. All
of these
On Tue, Oct 4, 2016 at 5:30 PM, Alexei Starovoitov
wrote:
> On Tue, Aug 23, 2016 at 04:08:21PM -0700, John Stultz wrote:
>> When I added some extra sanity checking in timekeeping_get_ns() under
>> CONFIG_DEBUG_TIMEKEEPING, I missed that the NMI safe __ktime_get_fast_ns()
>> method was using timeke
On Tue, 2016-10-04 at 20:34 -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> From : Andy Lutomirski
OK, I am not sure why "guilt patchbomb" (which invokes
git patchbomb) would do that :(
Obviously these first four patches are Andy's, not my
own.
--
All Rights Reversed.
signature.asc
D
On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
> devicemapper is using uevents for:
> a. dm-verity detected corruption
> b. dm-multipath: path failed or reinstated
> c. dm device renamed
> d. there's also some use in md and bcache.
>
> devicemapper uses DM_EVENT ioctl (yuck) for:
> 1.
On 04-10-16, 15:41, Lee Jones wrote:
> On Mon, 03 Oct 2016, Viresh Kumar wrote:
>
> > On 16-09-16, 08:56, Viresh Kumar wrote:
> > > These can fit in a single line (80 columns), don't split lines
> > > unnecessarily.
> > >
> > > Signed-off-by: Viresh Kumar
> > >
> > > ---
> > > V1->V2: New patch
Quoting John Stultz (john.stu...@linaro.org):
> This patch adds CAP_GROUP_MIGRATE_TASK and logic to allows a process
> to migrate other tasks between cgroups.
>
> In Android (where this feature originated), the ActivityManager tracks
> various application states (TOP_APP, FOREGROUND, BACKGROUND, S
From: Rik van Riel
>From : Andy Lutomirski
The crypto code was checking both use_eager_fpu() and
defined(X86_FEATURE_EAGER_FPU). The latter was nonsensical, so
remove it. This will avoid breakage when we remove
X86_FEATURE_EAGER_FPU.
Signed-off-by: Rik van Riel
Signed-off-by: Andy Lutomirsk
From: Andy Lutomirski
Since commit 58122bf1d856 ("x86/fpu: Default eagerfpu=on on all
CPUs") in Linux 4.6, eager FPU mode has been the default on all x86
systems, and no one has reported any regressions.
This patch removes the ability to enable lazy mode: use_eager_fpu()
becomes "return true" an
From: Rik van Riel
With the removal of the lazy FPU code, this field is no longer used.
Get rid of it.
Signed-off-by: Rik van Riel
---
arch/x86/kvm/x86.c | 4 +---
include/linux/kvm_host.h | 1 -
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/
This series removes lazy FPU mode, and cleans up various bits
and pieces around the FPU code.
I have run this through a basic floating point test that involves
about 1.5 billion context switches and 45 minutes of swapping at
250MB/second.
This seems to tease out bugs fairly well, though I would n
From: Andy Lutomirski
This removes all the obvious code paths that depend on lazy FPU mode.
It shouldn't change the generated code at all.
Signed-off-by: Rik van Riel
Signed-off-by: Andy Lutomirski
---
arch/x86/crypto/crc32c-intel_glue.c | 17 -
arch/x86/include/asm/fpu/intern
From: Andy Lutomirski
Now that lazy mode is gone, we don't need to distinguish which
xfeatures require eager mode.
Signed-off-by: Rik van Riel
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/fpu/xstate.h | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git
From: Rik van Riel
Now that CR0.TS is no longer being manipulated, we can simplify
switch_fpu_prepare by no longer nesting the handling of the new
fpu inside the two branches for the old FPU.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu/internal.h | 22 --
1 fil
From: Rik van Riel
Now that fpregs_activate and fpregs_deactivate do nothing except
call the double underscored versions of themselves, we can get
rid of the double underscore version.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu/internal.h | 25 +++--
1 file ch
From: Rik van Riel
With the lazy FPU code gone, we no longer use the counter field
in struct fpu for anything. Get rid it.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu/internal.h | 3 ---
arch/x86/include/asm/fpu/types.h| 11 ---
arch/x86/include/asm/trace/fpu.h|
From: Rik van Riel
Name the functions after the state they track, rather than the function
they currently enable. This should make it more obvious when we use the
fpu_register_state_valid function for something else in the future.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu/intern
On Tue, Oct 4, 2016 at 5:24 PM, Luis R. Rodriguez wrote:
>
> Note that the races are beyond firmware, so all
> kernel_read_file_from_path() users, as such re-using such old /sys/
> interafeces for firmware will not suffice to cover all ground now for
> the same race for other possible users.
Blah
On Tue, Aug 23, 2016 at 04:08:21PM -0700, John Stultz wrote:
> When I added some extra sanity checking in timekeeping_get_ns() under
> CONFIG_DEBUG_TIMEKEEPING, I missed that the NMI safe __ktime_get_fast_ns()
> method was using timekeeping_get_ns().
>
> Thus the locking added to the debug checks
On Tue, Oct 4, 2016 at 5:12 PM, Linus Torvalds
wrote:
> On Tue, Oct 4, 2016 at 5:00 PM, Luis R. Rodriguez wrote:
>>
>> I am not sure how/why a firmware loading daemon would be a better
>> idea now. What Marc describes that Josh proposed with signals for
>> userspcae seems more aligned with what w
This patch adds CAP_GROUP_MIGRATE_TASK and logic to allows a process
to migrate other tasks between cgroups.
In Android (where this feature originated), the ActivityManager tracks
various application states (TOP_APP, FOREGROUND, BACKGROUND, SYSTEM,
etc), and then as applications change states, the
On Tue, Oct 4, 2016 at 5:00 PM, Luis R. Rodriguez wrote:
>
> I am not sure how/why a firmware loading daemon would be a better
> idea now. What Marc describes that Josh proposed with signals for
> userspcae seems more aligned with what we likely need
Quite frankly, I doubt you want a signal.
You
From: David Howells
Date: Tue, 04 Oct 2016 17:01:30 +0100
> What's the procedure for sending more fixes at this point? Do I send them
> against net-next, since net doesn't contain the things to be fixed yet, or do
> I wait for net to catch up?
I'm sending Linus a pull request later today for th
On Sat, Sep 24, 2016 at 10:41:46AM -0700, Dmitry Torokhov wrote:
> On Fri, Sep 23, 2016 at 6:37 PM, Herbert, Marc wrote:
> > On 03/09/2016 11:10, Dmitry Torokhov wrote:
> >> I was thinking if we kernel could post
> >> "conditions" (maybe simple stings) that it waits for, and userspace
> >> could u
Hi,
After hibernation I get the following error when I tried to connect to monitor
through hdmi:
$ xrandr --output LVDS1 --off --output HDMI1 --auto
xrandr: Configure crtc 1 failed
This does not happen in kernel in kernel v4.6.7 but do happen in kernels v4.7.4
and v4.8.0
I don't see anything
On 10/04/2016 12:20 AM, Greg KH wrote:
On Mon, Oct 03, 2016 at 12:22:51PM -0700, Andy Grover wrote:
Hi Mike and GregKH,
I want a way to get devicemapper events without using the DM ioctl,
because that requires creating a thread to sleep in the ioctl for each
dm device I want events from.
It wo
Add support for lzma compressed uImage.
Support for gzip was already available but could not be enabled because
we were missing CONFIG_HAVE_KERNEL_GZIP in arch/arc/Kconfig.
Signed-off-by: Daniel Mentz
Cc: linux-snps-...@lists.infradead.org
Cc: Vineet Gupta
---
arch/arc/Kconfig | 2 ++
a
On Fri, Sep 23, 2016 at 07:51:41PM -0700, Herbert, Marc wrote:
> On 06/09/2016 16:04, Luis R. Rodriguez wrote:
> > They claim that without it there is the race between /lib/firmware
> > being ready and driver asking for the firmware.
>
> Hope it's understood by now.
>
> > I was told there were qu
On Tue, Oct 04, 2016 at 09:55:36PM +, Winkler, Tomas wrote:
>
> > On Tue, Oct 04, 2016 at 08:19:46AM +0300, Jarkko Sakkinen wrote:
> >
> > > > Make the driver uncallable first. The worst race that can happen is
> > > > that open("/dev/tpm0", ...) returns -EPIPE. I do not consider this
> > > >
On Tue, Oct 04, 2016 at 02:47:03PM -0700, Linus Torvalds wrote:
> Al,
> I'm assuming I'll be getting this from you. If not, just holler and
> I'll apply it directly.
Already applied in a local branch.
Hi Benjamin, Kent, and others,
Would you please comment / answer about this possible problem?
Any feedback is appreciated.
Since commit e1bdd5f27a5b ("aio: percpu reqs_available") the maximum
number of aio nr_events may be a function of num_possible_cpus() and
actually be /inversely proportional
On Tue, Oct 04, 2016 at 01:50:12PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Sep 22, 2016 at 05:36:48PM +0200, Jiri Olsa escreveu:
> > Adding dcacheline dimension key support. It
> > displays cacheline address as hex number.
> >
> > Using c2c wrapper to standard 'dcacheline' object
> > to d
Block comments should align the * on each line as reported by checkpatch
Signed-off-by: Jakub Jedelsky
---
drivers/staging/comedi/drivers/cb_pcidda.c | 4 ++--
drivers/staging/comedi/drivers/mite.c | 2 +-
drivers/staging/comedi/drivers/pcl818.c| 6 +++---
3 files changed, 6 insertions(
1 - 100 of 515 matches
Mail list logo
