From: "Roger Pau Monné" <roger.pau@citrix.com> To: Olaf Hering <olaf@aepfle.de> Cc: xen-devel@lists.xenproject.org Subject: Re: how to disable build of pv-shim? Date: Tue, 14 May 2019 12:42:39 +0200 [thread overview] Message-ID: <20190514104239.wasngivmlmnnez5u@Air-de-Roger> (raw) In-Reply-To: <20190514123406.72eda0f8.olaf@aepfle.de> On Tue, May 14, 2019 at 12:34:06PM +0200, Olaf Hering wrote: > Am Mon, 13 May 2019 17:20:05 +0200 > schrieb Roger Pau Monné <roger.pau@citrix.com>: > > > enabled by default > > Does anyone actually require it at all? Hm, that's the default behavior so far (enabled on x86), so I would like to keep it as-is. > Those who do pass --enable-pvshim to configure. No need for (incorrect) host_cpu checks. Using target_cpu should be fine I think. Thanks, Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Roger Pau Monné" <roger.pau@citrix.com> To: Olaf Hering <olaf@aepfle.de> Cc: xen-devel@lists.xenproject.org Subject: Re: [Xen-devel] how to disable build of pv-shim? Date: Tue, 14 May 2019 12:42:39 +0200 [thread overview] Message-ID: <20190514104239.wasngivmlmnnez5u@Air-de-Roger> (raw) Message-ID: <20190514104239.EuYJJm2Q5AzAc-eZjRwqYEzqJ1pAl-ssdKIUEmDs-KU@z> (raw) In-Reply-To: <20190514123406.72eda0f8.olaf@aepfle.de> On Tue, May 14, 2019 at 12:34:06PM +0200, Olaf Hering wrote: > Am Mon, 13 May 2019 17:20:05 +0200 > schrieb Roger Pau Monné <roger.pau@citrix.com>: > > > enabled by default > > Does anyone actually require it at all? Hm, that's the default behavior so far (enabled on x86), so I would like to keep it as-is. > Those who do pass --enable-pvshim to configure. No need for (incorrect) host_cpu checks. Using target_cpu should be fine I think. Thanks, Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-14 10:42 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-13 14:53 how to disable build of pv-shim? Olaf Hering 2019-05-13 14:53 ` [Xen-devel] " Olaf Hering 2019-05-13 15:07 ` Wei Liu 2019-05-13 15:07 ` [Xen-devel] " Wei Liu 2019-05-13 15:20 ` Roger Pau Monné 2019-05-13 15:20 ` [Xen-devel] " Roger Pau Monné 2019-05-13 15:28 ` Wei Liu 2019-05-13 15:28 ` [Xen-devel] " Wei Liu 2019-05-14 8:55 ` Roger Pau Monné 2019-05-14 8:55 ` [Xen-devel] " Roger Pau Monné 2019-05-14 9:23 ` Wei Liu 2019-05-14 9:23 ` [Xen-devel] " Wei Liu 2019-05-14 9:37 ` Andrew Cooper 2019-05-14 9:37 ` [Xen-devel] " Andrew Cooper 2019-05-14 9:52 ` Jan Beulich 2019-05-14 9:52 ` [Xen-devel] " Jan Beulich 2019-05-14 10:35 ` Roger Pau Monné 2019-05-14 10:35 ` [Xen-devel] " Roger Pau Monné 2019-05-14 9:26 ` Jan Beulich 2019-05-14 9:26 ` [Xen-devel] " Jan Beulich 2019-05-14 11:11 ` Roger Pau Monné 2019-05-14 11:11 ` [Xen-devel] " Roger Pau Monné 2019-05-14 11:21 ` Jan Beulich 2019-05-14 11:21 ` [Xen-devel] " Jan Beulich 2019-05-14 10:34 ` Olaf Hering 2019-05-14 10:34 ` [Xen-devel] " Olaf Hering 2019-05-14 10:42 ` Roger Pau Monné [this message] 2019-05-14 10:42 ` Roger Pau Monné 2019-05-15 10:18 ` Olaf Hering 2019-05-15 10:18 ` [Xen-devel] " Olaf Hering 2019-08-14 7:51 ` Olaf Hering 2019-08-14 7:57 ` Roger Pau Monné
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190514104239.wasngivmlmnnez5u@Air-de-Roger \ --to=roger.pau@citrix.com \ --cc=olaf@aepfle.de \ --cc=xen-devel@lists.xenproject.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).