Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3115937imm; Sun, 17 Jun 2018 11:25:02 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI8BQ3/iJLQM8AoE0kQf34mbpW0Q5xXgA4bU0J7nxlJvdj47u7EkAgWlS8GPXc0tJHIpmMS X-Received: by 2002:a62:9804:: with SMTP id q4-v6mr10465979pfd.65.1529259902751; Sun, 17 Jun 2018 11:25:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529259902; cv=none; d=google.com; s=arc-20160816; b=hlo58KuR1C7S8iqDN9qar6Ik2wYy1FemV3QwCW7c5NwDUcptwJo2QsyTkZpKP3x8ZL IY9jOL+aDy9piEqCGQK1EnKVDlQayxEJnJ/N7TTUfzpH8pMtwkt1jyBJcIrdpOmnq3sT dk2/6eBvfGRqXYso7lfmtCcwwoJJQENlJhsUlHVwZmHs5nTJGX189NVek3k5UpwaiHAh dOA6MwUrk8GQKqgNN/sG70OxC34YypplAYqmzNeoPsLUMwIcNI4g73otuiauTXiYaOWM GUCEggMJqy1cUsyzPXvzleXU70a75W42WghhjVHEvYdDiMKkV7UNSM3ZiNB7Yu3ne7mt RSjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=F3b9mSDTLxAXC3vPoImR7BVGUYWlsn2TsGSfQvsIQ+I=; b=w/mQMBZJro53GUSRfO5P4f+61oF6viHWD4MI8f9NqxmlkziZI2EHzTVXwCK8TFPFhr TzWy89LAqaT932NQCFSvaKUo5sUs0jE37wSRUG3xFRa3/2MbnoSmfB1hg6lxM0V3HglC cz7zsTV4WfBQYwrxFoYiZvlAesxynTeu4cA58VGpzwxmXvbcNCX+1Rn4YA4kbLt6kiMy +o/X94wAOUYsmUQl9W4NC3K90t/hk5hWzS8oiDmaQirx75Q1cyGaCxQyrLlIVa7uV04q Xi2EOFLQhHFS7WlTI7V6WD4XBTLrkyhRcVFu4U0jkivndqra/vRht1FX1rBQV8cvlecx jlCw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@juliacomputing-com.20150623.gappssmtp.com header.s=20150623 header.b="P5B3/gQd"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k24-v6si13374078pls.330.2018.06.17.11.24.47; Sun, 17 Jun 2018 11:25:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@juliacomputing-com.20150623.gappssmtp.com header.s=20150623 header.b="P5B3/gQd"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934190AbeFQSWq (ORCPT + 99 others); Sun, 17 Jun 2018 14:22:46 -0400 Received: from mail-it0-f68.google.com ([209.85.214.68]:33065 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933681AbeFQSWm (ORCPT ); Sun, 17 Jun 2018 14:22:42 -0400 Received: by mail-it0-f68.google.com with SMTP id k17-v6so9701297ita.0 for ; Sun, 17 Jun 2018 11:22:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juliacomputing-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F3b9mSDTLxAXC3vPoImR7BVGUYWlsn2TsGSfQvsIQ+I=; b=P5B3/gQdUXHo+G8jxiWSdOaisnbJy+GQiLr4oRHLylEsWb75nY/2/Sd8+eoP0/XtPk Psa6YAHN3Vg07jnz7eZX+ceD94GkVTR1mUS3H1Fo9eGY4tX7iEXfr7fB5GLcPj8VEglT bI2kQIYkOapiD0h9gIqZ81uDS4xTWf6MNeZddEsc+qR4XSLiXrABlGg4/O698clc9d/Y UGPIKW3rubyahoMKpoPu9TE84eIlXtjWLssLVnlVZfVbZDBKJrQH5ldr3zWvvX9DWpWZ 7sn1xrPjuWDZnCYTq2EJmz9S4otuAvwtOv0AWX3/xZ+I5DzExyR9D3kzoMWJSZYsAOvS yjeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F3b9mSDTLxAXC3vPoImR7BVGUYWlsn2TsGSfQvsIQ+I=; b=M8sc/1rtGSBl34Og5PsD2D2t5xfmB8Wg0oUDv8A75G9zPfAJ2OEIkJEUDuLPGK4eUq suAJHA4CsdL/5staLWShZAhF1gBv3bH2x/yamrR4pNOXZO1xWTMqro/tvK/zaNQQ23rz 3nvfiBojB0K+fAcINSMMfA0TM5Iv8fk0D5nY55v0qonVxdSHqlrwTcw9/CKaUqQqEunQ 92YEGTpFVRiO2IHtL+9wMsSfTvqJQmV0Kism9G7x9+h0R1zcj8Z281rM/VLWGSXtVyJA WQnRSA5kLvMMHpEip/dykRYA7TNX657veiAzIAuJ5LmYtSzrB28l3p0Mav1e7R3I1Ftt tr4g== X-Gm-Message-State: APt69E2FODAgis0r2Wfffa8p4w+0AgYDXO8Pfo2Sa21i3UzPICgDepey SCNIRGrTJc0JUPrj/UhT94yM6qRt03T7y2m2XFl4z490dfcfmA== X-Received: by 2002:a24:2f12:: with SMTP id j18-v6mr7764768itj.28.1529259761873; Sun, 17 Jun 2018 11:22:41 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:494a:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 11:22:01 -0700 (PDT) In-Reply-To: References: <1529195582-64207-1-git-send-email-keno@alumni.harvard.edu> <20180617163530.rvwf7fcukmoletgo@two.firstfloor.org> From: Keno Fischer Date: Sun, 17 Jun 2018 14:22:01 -0400 Message-ID: Subject: Re: [RFC PATCH] x86/arch_prctl: Add ARCH_SET_XCR0 to mask XCR0 per-thread To: Andi Kleen Cc: Linux Kernel Mailing List , Thomas Gleixner , Ingo Molnar , x86@kernel.org, "H. Peter Anvin" , Borislav Petkov , Dave Hansen , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Kyle Huey , "Robert O'Callahan" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Almost difference in CPU behavior > between the replayer and the replayee. Not sure what happened to this sentence. What I meant to say was: Almost any difference in CPU behavior between the replayer and the replayee will cause problems for the determinism of the trace. To elaborate on this, even if a register whose content differs between the recording and the replay, it can still cause problems down the line, e.g. if it is spilled to the stack and that stack address is then re-used later. In order for rr to work, we basically rely on the CPU behaving *exactly* the same during the record and the replay (down to counting performance counters the same). This works well, but there are corner cases (like this XCR0 one).