From: Greg Bellows <greg.bellows@linaro.org>
To: qemu-devel@nongnu.org, serge.fdrv@gmail.com,
edgar.iglesias@gmail.com, aggelerf@ethz.ch,
peter.maydell@linaro.org
Cc: Greg Bellows <greg.bellows@linaro.org>
Subject: [Qemu-devel] [PATCH v4 08/15] target-arm: Add feature unset function
Date: Mon, 15 Dec 2014 17:09:45 -0600 [thread overview]
Message-ID: <1418684992-8996-9-git-send-email-greg.bellows@linaro.org> (raw)
In-Reply-To: <1418684992-8996-1-git-send-email-greg.bellows@linaro.org>
Add an unset_feature() function to compliment the set_feature() function. This
will be used to disable functions after they have been enabled during
initialization.
Signed-off-by: Greg Bellows <greg.bellows@linaro.org>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
---
target-arm/cpu.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/target-arm/cpu.c b/target-arm/cpu.c
index d3db279..01afed2 100644
--- a/target-arm/cpu.c
+++ b/target-arm/cpu.c
@@ -327,6 +327,11 @@ static inline void set_feature(CPUARMState *env, int feature)
env->features |= 1ULL << feature;
}
+static inline void unset_feature(CPUARMState *env, int feature)
+{
+ env->features &= ~(1ULL << feature);
+}
+
static void arm_cpu_initfn(Object *obj)
{
CPUState *cs = CPU(obj);
--
1.8.3.2
next prev parent reply other threads:[~2014-12-15 23:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:09 [Qemu-devel] [PATCH v4 00/15] target-arm: Add CPU security extension enablement Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 01/15] target-arm: Add vexpress class and machine types Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 02/15] target-arm: Add vexpress a9 & a15 machine objects Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 03/15] target-arm: Switch to common vexpress machine init Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 04/15] target-arm: Add vexpress machine secure property Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 05/15] target-arm: Change vexpress daughterboard init arg Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 06/15] target-arm: Add virt class and machine types Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 07/15] target-arm: Add virt machine secure property Greg Bellows
2014-12-15 23:09 ` Greg Bellows [this message]
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 09/15] target-arm: Add ARMCPU " Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 10/15] target-arm: Add arm_boot_info secure_boot control Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 11/15] target-arm: Enable CPU has_el3 prop during VE init Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 12/15] target-arm: Set CPU has_el3 prop during virt init Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 13/15] target-arm: Breakout integratorcp and versatilepb cpu init Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 14/15] target-arm: Disable EL3 on unsupported machines Greg Bellows
2014-12-15 23:09 ` [Qemu-devel] [PATCH v4 15/15] target-arm: add cpu feature EL3 to CPUs with Security Extensions Greg Bellows
2014-12-16 18:42 ` [Qemu-devel] [PATCH v4 00/15] target-arm: Add CPU security extension enablement Peter Maydell
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=1418684992-8996-9-git-send-email-greg.bellows@linaro.org \
--to=greg.bellows@linaro.org \
--cc=aggelerf@ethz.ch \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=serge.fdrv@gmail.com \
/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: link
Be 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).