summaryrefslogtreecommitdiff
path: root/Makefile
blob: 133e497ea5a456b53487a5539d796c61c76081a3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
# Paths
prefix	= $(HOME)
BINDIR	= ${prefix}/bin
DESTDIR	=

CC := gcc
INSTALL := install

CFLAGS := -g -Wall -D_USE_SOURCE

DEBUG = false

ifeq ($(strip $(DEBUG)),true)
	CFLAGS  += -DDEBUG
endif

PROGRAMS := inotail #inotail-old inotify-watchdir simpletail

all: $(PROGRAMS)

inotail: inotail.o

inotail-old: inotail-old.o

inotify-watchdir: inotify-watchdir.o

simpletail: simpletail.o

%.o: %.c
	$(CC) $(CFLAGS) -c $< -o $@

install: inotail
	${INSTALL} -m 775 inotail ${DESTDIR}${BINDIR}

clean:
	rm -f *.o
	rm -f $(PROGRAMS)
.cgi/linux/net-next.git/commit/?id=ea26e4ec08d4727e3a9e48a6b74695861effcbd9'>ea26e4ec08d4727e3a9e48a6b74695861effcbd9 (diff)
kvm: nVMX: VMCLEAR an active shadow VMCS after last use
After a successful VM-entry with the "VMCS shadowing" VM-execution control set, the shadow VMCS referenced by the VMCS link pointer field in the current VMCS becomes active on the logical processor. A VMCS that is made active on more than one logical processor may become corrupted. Therefore, before an active VMCS can be migrated to another logical processor, the first logical processor must execute a VMCLEAR for the active VMCS. VMCLEAR both ensures that all VMCS data are written to memory and makes the VMCS inactive. Signed-off-by: Jim Mattson <jmattson@google.com> Reviewed-By: David Matlack <dmatlack@google.com> Message-Id: <1477668579-22555-1-git-send-email-jmattson@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat