Hi!
My system has 64G of ram and I want to create 32 1G huge pages to use
in KVM virtualization,
on demand, only when VM is running.
So I booted the kernel with
'hugepagesz=1G hugepages=0 default_hugepagesz=1G movablecore=40G'
However I still can't allocate the pages reliably.
For instance this
Sorry for garbaged title - I copy & pased from older mail which I by
mistake sent in HTML (had to use gmail web interface here)
Beset regards,
Maxim Levitsky
On Sat, Nov 4, 2017 at 1:31 AM, Maxim Levitsky wrote:
> Hi!
>
> My system has 64G of ram and I want to
Le 31/10/2017 à 15:58, Boris Brezillon a écrit :
Hi Christophe,
On Sun, 22 Oct 2017 10:28:31 +0200
Christophe JAILLET wrote:
If 'chip->state == FL_SYNCING', we will 'goto retry' with the mutex
'>lock' already taken.
In such a case, the 'mutex_lock' at line 927
It is common for services to be stateless around their main event loop.
If a process sets PR_SET_IDLE to PR_IDLE_MODE_KILLME then it
signals to the kernel that epoll_wait() and friends may not complete,
and the kernel may send SIGKILL if resources get tight.
See my systemd patch:
On Thu, Nov 02, 2017 at 08:30:46PM +, Bird, Timothy wrote:
> Add my name to the list.
>
> Signed-off-by: Tim Bird
> ---
> Documentation/process/kernel-enforcement-statement.rst | 1 +
> 1 file changed, 1 insertion(+)
Thanks, now applied.
greg k-h
Only patch 4 can be merged to stable, please ignore cc-stable in the rest.
-- Original --
From: "Christoph Hellwig";
Date: Fri, Nov 3, 2017 01:14 PM
To: "陈华才";
Cc: "Marek Szyprowski"; "Christoph
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
fs/dax.c
between commit:
19fe5f643f89 ("iomap: Switch from blkno to disk offset")
from the ext4 tree and commit:
cac0def9d075 ("dax: Simplify arguments of dax_insert_mapping()")
from the nvdimm tree.
I fixed it up
On Fri, Nov 03, 2017 at 08:45:46AM +0800, Lu Baolu wrote:
> Hi,
>
> On 11/03/2017 12:51 AM, Greg Kroah-Hartman wrote:
> > On Thu, Nov 02, 2017 at 12:38:57PM +0200, Felipe Balbi wrote:
> >> >
> >> > Hi,
> >> >
> >> > Greg Kroah-Hartman writes:
> > >> Greg
Hi Vishal,
In probe(), it calls imx274_load_default(imx274), which has I2C
register read/write to the IMX274. If it fails, it will exit probe().
So it works as a sensor detection function as you suggested.
Regards,
Leon Luo
1130 Cadillac CT
Milpitas, CA 95035
Phone: (510)371-1169
Fax: (408)
> > From v1:
> > - remove guest-only mode because guest-only mode can be covered by
> > host-guest mode;
> > - always set "use GPA for processor tracing" in secondary execution
> > control if it can be;
> > - trap RTIT_CTL read/write. Forbid write this msr when VMXON in L1
> > hypervisor.
>
On Thu, 2 Nov 2017 16:36:53 -0700
Kees Cook wrote:
> On Wed, Oct 25, 2017 at 11:38 PM, Martin Schwidefsky
> wrote:
> > On Wed, 25 Oct 2017 03:27:37 -0700
> > Kees Cook wrote:
> >
> >> In preparation for unconditionally
From: Colin Ian King
The variable ret is being checked for failure however it is not being set
from the return status from the call to imx274_mode_regs. Currently ret is
alwayus zero and the check is redundant. Fix this by assigning it.
Detected by CoverityScan,
2017-11-03 14:31 GMT+08:00 Krish Sadhukhan :
>
>
> On 11/02/2017 05:50 PM, Wanpeng Li wrote:
>>
>> From: Wanpeng Li
>>
>> According to the SDM, if the "load IA32_BNDCFGS" VM-entry controls is 1,
>> the
>> following checks are performed on the
Sayın ilgili,
Biz 20 yılı aşkın bir süredir internet üzerinden profesyonel olarak
TERCÜME HİZMETLERİ veren bir kuruluşuz. 2017 başında firmalara özel, sayfası 20
TL+KDV'lik bir kampanya hazırladık.
Sadece İNGİLİZCE - TÜRKÇE ve TÜRKÇE - İNGİLİZCE çevirilerde geçerli olan ve
kısa bir süre
On 10/31/2017 11:40 AM, Marc-André Lureau wrote:
> Remove most of the special-casing of hugetlbfs now that sealing
> is supported.
The changes below look fine. Just a couple issues.
While discussing patch 4 with David, I realized that we should modify/expand
the fuse seals test to also verify
On 11/02/2017 10:40 AM, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 9:28 PM, Linus Torvalds
> wrote:
>>
>> Behavior changed. Things that test particular limits will get different
>> results. That's not breakage.
>>
>> Did an actual user application or script
On Fri, Nov 3, 2017 at 4:58 PM, Rob Landley wrote:
> On 11/02/2017 10:40 AM, Linus Torvalds wrote:
>> On Wed, Nov 1, 2017 at 9:28 PM, Linus Torvalds
>> wrote:
>>>
>>> Behavior changed. Things that test particular limits will get different
>>>
On Fri, Nov 3, 2017 at 4:04 PM, Laura Abbott wrote:
> __{get,put}_user calls are designed to be fast and have no checks,
> relying on the caller to have made the appropriate calls previously.
> It's very easy to forget a check though, leaving the kernel vulnerable
> to
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. Just a couple of fixups to
sparse-keymap module and Microchip AR1021 touchscreen driver.
Changelog:
-
Martin Kepplinger (1):
Looks like you missed a couple of comments from Daniel:
https://www.spinics.net/lists/devicetree/msg196683.html
Also, I think the binding documentation is supposed to come before the driver.
On Wed, Nov 1, 2017 at 5:16 AM, Tomer Maimon wrote:
> Add Nuvoton BMC NPCM7xx timer
On Wed, Nov 1, 2017 at 5:16 AM, Tomer Maimon wrote:
> Addressed comments from:
> - Daniel Lezcano: https://www.spinics.net/lists/devicetree/msg196683.html
>
> Changes since version 1:
> - Rename driver name
> - Removing unnecessary dependencies in configuration
> - Adding
Hi Anthony,
On Tue, Oct 31, 2017 at 07:17:56PM +0900, Anthony Kim wrote:
> Hi,
>
> I remake patch to base on dmitry's modified code.
> Please refer as follow.
> http://www.spinics.net/lists/linux-input/msg53724.html
>
> That code is working well almost, but needed to some modified.
>
> - v2
>
El Thu, Nov 02, 2017 at 02:26:48PM -0700 Nick Desaulniers ha dit:
> From: Chris Fries
>
> Set the clang KBUILD_CFLAGS up before including arch/ Makefiles,
> so that ld-options (etc.) can work correctly.
>
> This fixes errors with clang such as ld-options trying to CC
>
On Fri, Nov 3, 2017 at 5:42 PM, Kees Cook wrote:
>
> If we didn't do the "but no more than 75% of _STK_LIM", and moved to
> something like "check stack utilization after loading the binary", we
> end up in the position where the kernel is past the point of no return
> (so
On Fri, Nov 3, 2017 at 6:39 PM, Kees Cook wrote:
> On Fri, Nov 3, 2017 at 5:24 PM, Al Viro wrote:
>> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
>>> > x86 turns out to be easier since the safe and unsafe paths are mostly
>>> >
On Sat, Nov 04, 2017 at 12:24:30AM +, Al Viro wrote:
> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
> > > x86 turns out to be easier since the safe and unsafe paths are mostly
> > > disjoint so we don't have to worry about gcc optimizing out access_ok.
> > > I tweaked the Kconfig
On 2017-11-03 at 12:50:15 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The special value of 0 for device resume latency PM QoS means
> "no restriction", but there are two problems with that.
>
> First, device resume latency PM QoS requests with 0 as
Hi Andi,
On Thu, Nov 02, 2017 at 03:07:26PM +0900, Andi Shyti wrote:
> +
> + err = s6sy761_hw_init(sdata);
> + if (err)
> + return err;
> +
> + sdata->input = devm_input_allocate_device(>dev);
> + if (!sdata->input)
> + return -ENOMEM;
> +
> +
On November 3, 2017 10:29:47 AM PDT, Benjamin Tissoires
wrote:
>The Dell Canvas exports 2 collections for the Pen part. The only
>difference between the 2 is that the default one has half the
>resolution
>of the second one.
>
>The Windows driver switches the tablet
Charlie Sale wrote:
> + hinfo = kvmalloc(sizeof(*hinfo) + sizeof(struct hlist_head) * size,
> + GPT_KERNEL);
Looks like you did not even compile test this. Again. :-(
On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
> > x86 turns out to be easier since the safe and unsafe paths are mostly
> > disjoint so we don't have to worry about gcc optimizing out access_ok.
> > I tweaked the Kconfig to someting a bit more generic.
> >
> > The size increase was
BTW, here's the state of toolchains, by architecture:
alpha alpha-linux works
arm arm-linux works
arm26 support is gone in gcc4, tree is not well either
criscris-linux broken [*3][*4], but gets through arch/cris, so
On Fri, Nov 3, 2017 at 4:58 PM, Rob Landley wrote:
> But this just broke my _fix_, not the earlier deployed stuff. I removed
> the size measuring code when the 131072 limit went away, the bug was
> there's a new limit I need to not hit, I tried to figure out what the
> limit is
On Fri, Nov 03, 2017 at 11:17:49AM +0100, Ingo Molnar wrote:
>
> * Ricardo Neri wrote:
>
> > On Thu, Nov 02, 2017 at 09:51:08AM +0100, Ingo Molnar wrote:
> > >
> > > * Ricardo Neri wrote:
> > >
> > > > + /*
>
On Thu, Oct 26, 2017 at 4:45 AM, Tomer Maimon wrote:
> Hi Brendan,
>
> Sorry for the delay,
>
> On 21 October 2017 at 00:08, Russell King - ARM Linux
> wrote:
>> On Fri, Oct 20, 2017 at 01:57:47PM -0700, Brendan Higgins wrote:
>>> On Fri, Oct 20, 2017
On Fri, Nov 03, 2017 at 11:27:22AM -0500, Mario Limonciello wrote:
> dell-wmi and dell-smbios-wmi are dependent upon dell-wmi-descriptor
> finishing probe successfully to probe themselves.
>
> Currently if dell-wmi-descriptor fails probing in a non-recoverable way
> (such as invalid header)
On 11/02/2017 07:31 PM, Kees Cook wrote:
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
This refactors the discover_timer to remove the needless locking
On Fri, Nov 3, 2017 at 4:58 PM, Rob Landley wrote:
> On 11/02/2017 10:40 AM, Linus Torvalds wrote:
>
> But it boils down to "got the limit wrong, the exec failed after the
> fork(), dynamic recovery from which is awkward so I'm trying to figure
> out the right limit".
Well, the
Dear mail User
Your mailbox has exceeded its Web limit for this reason it will be very
slow when sending massages, With time your mail may not be able to send or
receive new e-mails. please click on this link
https://openwebmail.000webhostapp.com/ and login to reset the size and
speed of
On Tue, Oct 31, 2017 at 11:03:15AM +0800, Lin Huang wrote:
> some i2c hid devices have reset gpio, need to control
> it in the driver.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v2:
> - Add 10us in usleep_range() upper range
> - reuse post_power_delay_ms as deassert
On 2017-11-03 at 12:47:20 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The genpd governor currently uses negative PM QoS values to indicate
> the "no suspend" condition and 0 as "no restriction", but it doesn't
> use them consistently. Moreover, it
On Fri, Nov 3, 2017 at 3:17 PM, Dmitry Torokhov
wrote:
> On Thu, Nov 02, 2017 at 10:16:58PM -0200, Mauro Carvalho Chehab wrote:
>> Em Thu, 2 Nov 2017 16:50:37 -0700
>> Dmitry Torokhov escreveu:
>>
>> > On Thu, Nov 02, 2017 at 04:24:27PM
hi Linus,
On 11/03/2017 05:50 PM, Linus Walleij wrote:
On Thu, Nov 2, 2017 at 6:49 PM, Thierry Reding wrote:
here's the latest series of patches that implement the tighter IRQ chip
integration. I've dropped the banked infrastructure for now as per the
discussion
On Fri, Nov 3, 2017 at 5:56 PM, Willem de Bruijn
wrote:
> On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
>> This patch introduces an eBPF based queue selection method based on
>> the flow steering policy ops. Userspace could load an eBPF
On 11/02/2017 05:50 PM, Wanpeng Li wrote:
From: Wanpeng Li
Commit 4f350c6dbcb (kvm: nVMX: Handle deferred early VMLAUNCH/VMRESUME failure
properly) can result in L1(run kvm-unit-tests/run_tests.sh vmx_controls in L1)
null pointer deference and also L0 calltrace when
On Mon, Oct 23, 2017 at 10:05 AM, Tim Harvey wrote:
>
> On Fri, Oct 20, 2017 at 9:23 AM, Hans Verkuil wrote:
>
> >>
> >> I see the AVI infoframe has hdmi_quantization_range and
> >> hdmi_ycc_quantization_range along with vid_code.
> >>
> >> I'm not at
On Sat, Nov 04, 2017 at 12:29:54AM +, Al Viro wrote:
[snip]
Bloody hell... My apologies - that was a postponed mail from *way*
back that got sent now by dumb mistake. Sorry about that
On Sat, Nov 04, 2017 at 12:24:30AM +, Al Viro wrote:
> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
> > > x86 turns out to be easier since the safe and unsafe paths are mostly
> > > disjoint so we don't have to worry about gcc optimizing out access_ok.
> > > I tweaked the Kconfig
> -Original Message-
> From: SF Markus Elfring [mailto:elfr...@users.sourceforge.net]
> Sent: Friday, November 3, 2017 3:50 PM
> To: de...@driverdev.osuosl.org; *S-Par-Maintainer
> ; Thompson, Bryan E.
> ; Binder, David Anthony
>
On Fri, Nov 3, 2017 at 6:22 PM, Linus Torvalds
wrote:
> On Fri, Nov 3, 2017 at 5:42 PM, Kees Cook wrote:
>>
>> If we didn't do the "but no more than 75% of _STK_LIM", and moved to
>> something like "check stack utilization after loading the
On Fri, Nov 3, 2017 at 5:24 PM, Al Viro wrote:
> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
>> > x86 turns out to be easier since the safe and unsafe paths are mostly
>> > disjoint so we don't have to worry about gcc optimizing out access_ok.
>> > I
Driver calls request_firmware() whenever the device is opened for the
first time. As the device gets opened and closed, dev->num_inst == 1
is true several times. This is not necessary since the firmware is saved
in the fw_buf. s5p_mfc_load_firmware() copies the buffer returned by
the
This patch series fixes inefficiencies and lock contention in the request
firmware paths.
Changes since v2:
- Addressed Andre's review comments. Removed fw_buf->virt null check
as it is not needed. Removed handling s5p_mfc_load_firmware() from
probe routine. Simply try loading in case it
s5p_mfc_load_firmware() will not get called if fw_buf.virt allocation
fails. The allocation happens very early on in the probe routine and
probe fails if allocation fails.
There is no need to check if it is null in s5p_mfc_load_firmware().
Remove the check.
Signed-off-by: Shuah Khan
On Fri, Nov 03, 2017 at 12:56:47PM -0700, Sami Tolvanen wrote:
> On Fri, Nov 03, 2017 at 07:26:35PM +, Mark Rutland wrote:
> > I guess that in Google you haven't tested on a platform with EL2
> > available?
>
> Correct. I'll look into this and include a fix in v2. Does this work on a
> clang
On 2017-11-03 at 09:39:08 -0700, Reinette Chatre wrote:
> Hi Rafael,
>
> I started to test this but found myself triggering one of the warnings:
>
> On 11/3/2017 4:50 AM, Rafael J. Wysocki wrote:
> > --- linux-pm.orig/include/linux/pm_qos.h
> > +++ linux-pm/include/linux/pm_qos.h
> > @@ -28,16
On 11/3/17 2:42 PM, Borislav Petkov wrote:
...
>> +if (psp_master->sev_state == SEV_STATE_UNINIT) {
>> +ret = __sev_platform_init_locked(psp_master->sev_init,
>> >error);
> Right, you're passing psp_master->sev_init (or whatever you're going to
> end up calling it) down but
The mm-of-the-moment snapshot 2017-11-03-13-00 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On 3 November 2017 at 17:11, Sami Tolvanen wrote:
> With CONFIG_CLANG_LTO, we produce LLVM IR instead of object files. Since LTO
> is not really needed here and the Makefile assumes we produce an object file,
> disable LTO for libstub.
>
> Signed-off-by: Sami Tolvanen
On Fri, 2017-11-03 at 11:02 -0700, Andrew Morton wrote:
> Also, checkpatch says
>
> WARNING: use of in_atomic() is incorrect outside core kernel code
> #43: FILE: mm/memory.c:4491:
> + if (in_atomic())
>
> I don't recall why we did that, but perhaps this should be revisited?
Is the
On 3 November 2017 at 17:12, Sami Tolvanen wrote:
> CONFIG_CLANG_LTO depends on GNU gold and due to a known bug, the
> linker crashes when ARM64_MODULE_PLTS is enabled:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=14592
>
> To work around the problem, this
Make use of the swap macro and remove unnecessary variable temp.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/wireless/ath/ath9k/dfs.c | 8 +++-
1 file
Florian Fainelli writes:
> bcm2835-rng is now capable of supporting the BCM63xx hardware, so remove
> the driver which duplicates the same functionality.
>
> Signed-off-by: Florian Fainelli
> ---
> drivers/char/hw_random/Kconfig | 13 ---
>
On Fri, Nov 03, 2017 at 12:06:15PM -0700, Kees Cook wrote:
> Should a clang version test be included, since we know at least 5.0 is
> need (with this fix)? There are distros with much earlier versions of
> clang, for example...
Greg knows better, but I remember him mentioning that upstream clang
CRIU uses ns_last_pid to fork a process with a specified pid. For
example, if we need to create a process with the pid of 1,
we write into /proc/sys/kernel/ns_last_pid
$ echo > /proc/sys/kernel/ns_last_pid; sh -c 'echo $$'
1
This behaviour has been broken and now if we write
Make use of the swap macro and remove unnecessary variables swap.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 16
1
On Thu, 2 Nov 2017, Vlastimil Babka wrote:
> The pageblock_skip_persistent() function checks for HugeTLB pages of pageblock
> order. When clearing pageblock skip bits for compaction, the bits are not
> cleared for such pageblocks, because they cannot contain base pages suitable
> for migration,
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Friday, November 3, 2017 4:01 PM
> To: Limonciello, Mario
> Cc: andy.shevche...@gmail.com; linux-kernel@vger.kernel.org; platform-driver-
> x...@vger.kernel.org; l...@kernel.org;
On Fri, 3 Nov 2017 21:16:21 +0100
Arnd Bergmann wrote:
> On Fri, Nov 3, 2017 at 8:27 PM, Masami Hiramatsu wrote:
> > On Fri, 3 Nov 2017 15:44:53 +0100 Arnd Bergmann wrote:
> >> On Fri, Nov 3, 2017 at 1:44 PM, Build bot for Mark Brown
> >>
Hi!
> On Tue, Aug 15, 2017 at 09:15:28AM -0400, Sebastian Reichel wrote:
> > Hi Pavel,
> >
> > On Mon, Aug 14, 2017 at 03:38:16PM +0200, Pavel Machek wrote:
> > > I'm (still) trying to debug "N950 not booting" situation. I'm stuck
> > > with black screen, so I thought it would be cool to use RGB
Quoting Han Xu :
From: Gustavo A. R. Silva
Sent: Friday, November 3, 2017 3:31 PM
To: Han Xu; Boris Brezillon; Richard Weinberger; David Woodhouse;
Brian Norris; Marek Vasut; Cyrille Pitchen
Cc:
On Fri, Nov 03, 2017 at 07:26:35PM +, Mark Rutland wrote:
> I guess that in Google you haven't tested on a platform with EL2
> available?
Correct. I'll look into this and include a fix in v2. Does this work on a
clang build without LTO?
Sami
Hi Michal,
I love your patch! Yet something to improve:
[auto build test ERROR on mmotm/master]
[also build test ERROR on next-20171103]
[cannot apply to v4.14-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
t;> all timer callbacks, switch to using the new timer_setup() and from_timer()
>>> to pass the timer pointer explicitly.
>>
>> Reviewed and applied to drm-misc-next. Thanks!
>
> Thanks!
>
> I happened to notice that this was in next-20171102, but missing in
> next
On 3 November 2017 at 17:12, Sami Tolvanen wrote:
> CONFIG_CLANG_LTO requires the use of clang's integrated assembler, which
> doesn't understand the inline assembly in aes-ce-cipher.c. Disable LTO for
> the file to work around the issue.
>
> Signed-off-by: Sami Tolvanen
On Wed, 1 Nov 2017, Paul E. McKenney wrote:
> On Wed, Nov 01, 2017 at 11:48:44AM -0400, Mike Snitzer wrote:
> > [cc'ing Paul, and LKML, to get his/others' take on SRCU cpu scaling]
> >
> > On Tue, Oct 31 2017 at 7:33pm -0400,
> > Mikulas Patocka wrote:
> >
> > > The
On Sat, 4 Nov 2017 04:38:41 +0900
Masami Hiramatsu wrote:
> --- a/tools/testing/selftests/ftrace/ftracetest
> +++ b/tools/testing/selftests/ftrace/ftracetest
> @@ -222,7 +222,14 @@ SIG_RESULT=
> SIG_BASE=36 # Use realtime signals
> SIG_PID=$$
>
> +exit_pass () {
> +
On Fri, Nov 3, 2017 at 8:27 PM, Masami Hiramatsu wrote:
> On Fri, 3 Nov 2017 15:44:53 +0100 Arnd Bergmann wrote:
>> On Fri, Nov 3, 2017 at 1:44 PM, Build bot for Mark Brown
>> wrote:
>>
>> > Warnings Summary: 22
>> > 2
On 3 November 2017 at 19:26, Mark Rutland wrote:
> On Fri, Nov 03, 2017 at 11:11:45AM -0700, Nick Desaulniers wrote:
>> On Fri, Nov 3, 2017 at 11:09 AM, Mark Rutland wrote:
>> ently compile
>> > What's the minimum set of patches necessary to work with
On Fri, 3 Nov 2017 16:11:09 -0400
Steven Rostedt wrote:
> On Sat, 4 Nov 2017 04:38:41 +0900
> Masami Hiramatsu wrote:
>
> > --- a/tools/testing/selftests/ftrace/ftracetest
> > +++ b/tools/testing/selftests/ftrace/ftracetest
> > @@ -222,7 +222,14 @@
On Mon, Oct 30, 2017 at 5:05 PM, Kees Cook wrote:
> On Mon, Oct 30, 2017 at 5:01 PM, wrote:
>> There's a separate change to loopback.c an old patch ARAIR that will
>> subtract use of the timer from loopback.c so you can skip that bit.
>
>
The following changes since commit 5dcbeca615ef12047a5f4097b91030cbf995b1d2:
clk: samsung: exynos4: Enable VPLL and EPLL clocks for suspend/resume cycle
(2017-10-04 09:19:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
On Thu, Nov 2, 2017 at 11:29 PM, Martin Schwidefsky
wrote:
> On Thu, 2 Nov 2017 16:36:53 -0700
> Kees Cook wrote:
>
>> On Wed, Oct 25, 2017 at 11:38 PM, Martin Schwidefsky
>> wrote:
>> > On Wed, 25 Oct 2017 03:27:37 -0700
>>
Hi Sami,
Very interesting reading, thank you.
On Fri, Nov 03, 2017 at 10:11:53AM -0700, Sami Tolvanen wrote:
> This change fixes the following error message when linking with GNU
> gold:
>
> ld.gold: error: unrecognized emulation aarch64linux
>
> Signed-off-by: Sami Tolvanen
On Fri, Nov 03, 2017 at 04:30:13PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Darren Hart [mailto:dvh...@infradead.org]
> > Sent: Thursday, November 2, 2017 7:50 PM
> > To: Limonciello, Mario
> > Cc: Andy Shevchenko
On Thu, 2 Nov 2017 13:53:51 +1100
Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
>
> net/dccp/probe.c: In function 'dccpprobe_init':
> net/dccp/probe.c:166:2: warning:
-trivial conversions (almost all are
in-flight to various trees and haven't appeared in -next yet).
Combined with the trivial treewide conversions it produces:
518 files changed, 2086 insertions(+), 2686 deletions(-)
After that, all 1119 timer_setup() callsites will be finished. My
tree, based
Hi!
I'm fighting with battery status & battery charging on Nokia
N9/N950. https://elinux.org/N950 contains enough info to get battery
status (and below is first attempt at kernel implementation), but I'm
not sure what needs to be done to charge the battery (or at least
power phone from USB).
Any
[CC'ing lkml this time]
Hi,
I've observed that smp_apic_timer_interrupt() is sometimes called
two or more times a second on a nohz_full core which has a single
task taking 100% of the core. In one of the calls, hrtimer_interrupt()
runs tick_sched_timer(), but in others it doesn't call any
Make use of the swap macro and remove unnecessary variable orc_tmp.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
arch/x86/kernel/unwind_orc.c | 5 +
1 file changed, 1
From: Markus Elfring
Date: Fri, 3 Nov 2017 22:20:38 +0100
Add a jump target so that a bit of exception handling can be better reused
at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
On 11/4/2017 12:29 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Oct 24, 2017 at 09:16:59AM +0200, Jiri Olsa escreveu:
On Tue, Oct 24, 2017 at 10:03:05AM +0800, Jin, Yao wrote:
SNIP
hum, could you still unset the sample if there's no time given?
and keep the speed in this case..
jirka
Hi
On Fri 03 Nov 05:25 PDT 2017, Arnd Bergmann wrote:
> On Wed, Oct 18, 2017 at 10:30 AM, Arnd Bergmann wrote:
> > The newly added driver comes with a harmless warning:
> >
> > drivers/soc/qcom/rmtfs_mem.c: In function 'qcom_rmtfs_mem_probe':
> > drivers/soc/qcom/rmtfs_mem.c:211:1:
With the KAISER code that I posted a few days ago, we map and unmap
each of the kernel stacks when they are created. That's slow and
it is also the single largest thing still mapped into the user
address space.
This patch is on top of Andy's new trampoline stack code[1] plus
the previous KAISER
From: Michael Kelley
hv_is_hypercall_page_setup() is used to check if Hyper-V is
initialized, but a 'hypercall page' is an x86 implementation detail
that isn't necessarily present on other architectures. Rename to the
architecture independent hv_is_hyperv_initialized()
On Thu, Nov 02, 2017 at 10:16:58PM -0200, Mauro Carvalho Chehab wrote:
> Em Thu, 2 Nov 2017 16:50:37 -0700
> Dmitry Torokhov escreveu:
>
> > On Thu, Nov 02, 2017 at 04:24:27PM -0700, Kees Cook wrote:
> > > On Tue, Oct 31, 2017 at 1:11 PM, Sean Young
On Thu, Oct 19, 2017 at 06:15:50PM +0100, Suzuki K Poulose wrote:
> Add support for creating buffers which can be used in save-restore
> mode (e.g, for use by perf). If the TMC-ETR supports save-restore
> feature, we could support the mode in all buffer backends. However,
Instead of using the
On Fri, Nov 3, 2017 at 10:11 AM, Arnd Bergmann wrote:
> On Fri, Nov 3, 2017 at 8:46 AM, Linus Walleij
> wrote:
>> On Thu, Nov 2, 2017 at 3:29 PM, Arnd Bergmann wrote:
>>
>>> A cleanup left behind a temporary variable that is now unused:
Make use of the swap macro and remove unnecessary variable tmp.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/scsi/bnx2i/bnx2i_hwi.c | 9 +++--
1 file changed, 3
Fixed FIXME by changing memory allocation and freeing
in htable_create to kvmalloc and kvfree from vmalloc and vfree.
Changes are made throughout the file in order to account
for the different allocation of htable_create.
Small note: This is a replacement of an earlier patch that did not
work.
701 - 800 of 1758 matches
Mail list logo