From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 4/6] s390: add system call to run tasks with modified branch prediction Date: Wed, 17 Jan 2018 12:50:21 +0100 Message-ID: <299df1a8-f78d-15be-7217-6f201ea849c7@redhat.com> References: <1516182519-10623-1-git-send-email-schwidefsky@de.ibm.com> <1516182519-10623-5-git-send-email-schwidefsky@de.ibm.com> <5bda76be-0fec-8165-20bf-5cd8e51e955a@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Heiko Carstens , Cornelia Huck , Greg Kroah-Hartman , Jon Masters , Marcus Meissner , Jiri Kosina To: Christian Borntraeger , Florian Weimer , Martin Schwidefsky , linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 17/01/2018 12:14, Christian Borntraeger wrote: > > > On 01/17/2018 11:03 AM, Florian Weimer wrote: >> On 01/17/2018 10:48 AM, Martin Schwidefsky wrote: >>>          rc = syscall(__NR_s390_modify_bp); >>>          if (rc) { >>>                  perror("s390_modify_bp"); >>>                  exit(EXIT_FAILURE); >>>          } >> >> Isn't this traditionally done through personality or prctl? > > I think we want this per thread (and not per process). So I assume personality > will not work out. Can a prctl be done per thread? Yes, prctls can be either per-process (e.g. PR_SET_CHILD_SUBREAPER or PR_SET_DUMPABLE) or per-thread (e.g. PR_SET_NAME or PR_SET_SECCOMP). Paolo